From: Paul Moore <[email protected]>
To: [email protected], [email protected],
[email protected]
Cc: Arnd Bergmann <[email protected]>,
Greg Kroah-Hartman <[email protected]>
Subject: [PATCH 0/3] LSM hooks for IORING_OP_URING_CMD
Date: Mon, 22 Aug 2022 17:14:14 -0400 [thread overview]
Message-ID: <166120234006.357028.9335354304390109167.stgit@olly> (raw)
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
---
Luis Chamberlain (1):
lsm,io_uring: add LSM hooks for the new uring_cmd file op
Paul Moore (2):
/dev/null: add IORING_OP_URING_CMD support
selinux: implement the security_uring_cmd() LSM hook
drivers/char/mem.c | 6 ++++++
include/linux/lsm_hook_defs.h | 1 +
include/linux/lsm_hooks.h | 3 +++
include/linux/security.h | 5 +++++
io_uring/uring_cmd.c | 5 +++++
security/security.c | 4 ++++
security/selinux/hooks.c | 24 ++++++++++++++++++++++++
security/selinux/include/classmap.h | 2 +-
8 files changed, 49 insertions(+), 1 deletion(-)
next reply other threads:[~2022-08-22 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 21:14 Paul Moore [this message]
2022-08-22 21:17 ` [PATCH 0/3] LSM hooks for IORING_OP_URING_CMD Paul Moore
-- 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=166120234006.357028.9335354304390109167.stgit@olly \
[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