public inbox for [email protected]
 help / color / mirror / Atom feed
From: Paul Moore <[email protected]>
To: Casey Schaufler <[email protected]>
Cc: "Hamza Mahfooz" <[email protected]>,
	[email protected], [email protected],
	"Jens Axboe" <[email protected]>,
	"James Morris" <[email protected]>,
	"Serge E. Hallyn" <[email protected]>,
	"Pavel Begunkov" <[email protected]>,
	"Stephen Smalley" <[email protected]>,
	"Ondrej Mosnacek" <[email protected]>,
	"Thiébaud Weksteen" <[email protected]>,
	"Masahiro Yamada" <[email protected]>,
	"Bram Bonné" <[email protected]>,
	[email protected], [email protected]
Subject: Re: [PATCH] lsm,io_uring: add LSM hooks for io_uring_setup()
Date: Sat, 4 Jan 2025 21:12:26 -0500	[thread overview]
Message-ID: <CAHC9VhSWUNfFUZPtEQdHN4ON6VzWoRN38NeoHJHmGZj68NprYw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Thu, Dec 19, 2024 at 4:34 PM Casey Schaufler <[email protected]> wrote:
> On 12/19/2024 12:41 PM, Hamza Mahfooz wrote:
> > It is desirable to allow LSM to configure accessibility to io_uring.
>
> Why is it desirable to allow LSM to configure accessibility to io_uring?

Look at some of the existing access controls that some LSMs, including
Smack, have implemented to control access to certain parts of io_uring
such as credential sharing.  While having a control point at the top
of io_uring_setup() is a fairly coarse way to restrict io_uring, the
advantage is that it is very simple.

--
paul-moore.com

      reply	other threads:[~2025-01-05  2:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 20:41 [PATCH] lsm,io_uring: add LSM hooks for io_uring_setup() Hamza Mahfooz
2024-12-19 20:45 ` Jens Axboe
2024-12-19 21:34 ` Casey Schaufler
2025-01-05  2:12   ` Paul Moore [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHC9VhSWUNfFUZPtEQdHN4ON6VzWoRN38NeoHJHmGZj68NprYw@mail.gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox