From: Paul Moore <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: [GIT PULL] LSM fixes for v6.0 (#1)
Date: Mon, 29 Aug 2022 17:02:28 -0400 [thread overview]
Message-ID: <CAHC9VhQu7vuXMqpTzdZp2+M4pBZXDdWs7FtWdEt_3abW-ArUDA@mail.gmail.com> (raw)
Linus,
Four patches to add SELinux and Smack controls to the io_uring
IORING_OP_URING_CMD. Three of these patches are necessary as without
them the IORING_OP_URING_CMD remains outside the purview of the LSMs
(Luis' LSM patch, Casey's Smack patch, and my SELinux patch). These
patches have been discussed at length with the io_uring folks, and
Jens has given his thumbs-up on the relevant patches (see the commit
descriptions). There is one patch that is not strictly necessary, but
it makes testing much easier and is very trivial: the /dev/null
IORING_OP_URING_CMD patch. If you have a problem accepting the
/dev/null patch in a rcX release, let me know and I'll remove it.
As of earlier today the tag merged cleanly with your tree, so there
should be no surprises. Please merge for v6.0.
-Paul
--
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
tags/lsm-pr-20220829
for you to fetch changes up to dd9373402280cf4715fdc8fd5070f7d039e43511:
Smack: Provide read control for io_uring_cmd
(2022-08-26 14:56:35 -0400)
----------------------------------------------------------------
lsm/stable-6.0 PR 20220829
----------------------------------------------------------------
Casey Schaufler (1):
Smack: Provide read control for io_uring_cmd
Luis Chamberlain (1):
lsm,io_uring: add LSM hooks for the new uring_cmd file op
Paul Moore (2):
selinux: implement the security_uring_cmd() LSM hook
/dev/null: add IORING_OP_URING_CMD support
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 +-
security/smack/smack_lsm.c | 32 ++++++++++++++++++++++++++++++
9 files changed, 81 insertions(+), 1 deletion(-)
--
paul-moore.com
next reply other threads:[~2022-08-29 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 21:02 Paul Moore [this message]
2022-08-31 17:20 ` [GIT PULL] LSM fixes for v6.0 (#1) pr-tracker-bot
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=CAHC9VhQu7vuXMqpTzdZp2+M4pBZXDdWs7FtWdEt_3abW-ArUDA@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