From: Paul Moore <[email protected]>
To: [email protected], [email protected],
[email protected]
Cc: Arnd Bergmann <[email protected]>,
Greg Kroah-Hartman <[email protected]>
Subject: Re: [PATCH 0/3] LSM hooks for IORING_OP_URING_CMD
Date: Mon, 22 Aug 2022 17:17:39 -0400 [thread overview]
Message-ID: <CAHC9VhSj_qFaftPzdznxaTdYp_=a_7kqNc8Hbdh0Bp7sSf2z=Q@mail.gmail.com> (raw)
In-Reply-To: <166120234006.357028.9335354304390109167.stgit@olly>
On Mon, Aug 22, 2022 at 5:14 PM Paul Moore <[email protected]> wrote:
>
> This patchset includes three patches: one to add a new LSM hook for
> the IORING_OP_URING_CMD operation, one to add the SELinux
> implementation for the new hook, and one to enable
> IORING_OP_URING_CMD for /dev/null. The last patch, the /dev/null
> support, is obviously not critical but it makes testing so much
> easier and I believe is in keeping with the general motivation behind
> /dev/null.
>
> Luis' patch has already been vetted by Jens and the io_uring folks,
> so the only new bits are the SELinux implementation and the trivial
> /dev/null implementation of IORING_OP_URING_CMD. Assuming no one
> has any objections over the next few days, I'll plan on sending this
> up to Linus during the v6.0-rcX cycle.
>
> I believe Casey is also currently working on Smack support for the
> IORING_OP_URING_CMD hook, and as soon as he is ready I can add it
> to this patchset (or Casey can send it up himself).
>
> -Paul
Forgive me, I spaced and hit send on this patchset posting a *second*
too soon and didn't cancel it in time so the cover letter leaked out.
A proper patchset posting will be coming in just another minute ...
--
paul-moore.com
next prev parent reply other threads:[~2022-08-22 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 21:14 [PATCH 0/3] LSM hooks for IORING_OP_URING_CMD Paul Moore
2022-08-22 21:17 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 21:21 Paul Moore
2022-08-26 16:27 ` Paul Moore
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='CAHC9VhSj_qFaftPzdznxaTdYp_=a_7kqNc8Hbdh0Bp7sSf2z=Q@mail.gmail.com' \
[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