From: Paul Moore <paul@paul-moore.com>
To: stable@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
Luis Chamberlain <mcgrof@kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>,
selinux@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [v5.19.y PATCH 0/3] Backport the io_uring/LSM CMD passthrough controls
Date: Tue, 06 Sep 2022 17:03:36 -0400 [thread overview]
Message-ID: <166249766105.409408.12118839467847524983.stgit@olly> (raw)
The stable patch merging tools failed to automatically merge the
io_uring/LSM CMD passthrough controls into the stable v5.19.y branch,
so I'm doing the backport manually and submitting them directly to
stable for the next v5.19.y release. The backport is necessary due
to the reorg/decomposition of the io_uring code in io_uring/ during
the v5.19->v6.0 merge window. Other than the differences in the
filenames under io_uring, the code changes are pretty much the same.
I've done some basic sanity testing this afternoon with these
patches and everything looks good to me.
If you would prefer to pull these directly from a git tree instead
of email, they are available via the LSM tree on the stable-5.19
branch, using the lsm-pr-20220906 tag.
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
lsm-pr-20220906
---
Paul Moore (3):
lsm,io_uring: add LSM hooks for the new uring_cmd file op
selinux: implement the security_uring_cmd() LSM hook
Smack: Provide read control for io_uring_cmd
include/linux/lsm_hook_defs.h | 1 +
include/linux/lsm_hooks.h | 3 +++
include/linux/security.h | 5 +++++
io_uring/io_uring.c | 4 ++++
security/security.c | 4 ++++
security/selinux/hooks.c | 24 ++++++++++++++++++++++
security/selinux/include/classmap.h | 2 +-
security/smack/smack_lsm.c | 32 +++++++++++++++++++++++++++++
8 files changed, 74 insertions(+), 1 deletion(-)
next reply other threads:[~2022-09-06 21:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 21:03 Paul Moore [this message]
2022-09-06 21:03 ` [v5.19.y PATCH 1/3] lsm,io_uring: add LSM hooks for the new uring_cmd file op Paul Moore
2022-09-06 21:03 ` [v5.19.y PATCH 2/3] selinux: implement the security_uring_cmd() LSM hook Paul Moore
2022-09-06 21:03 ` [v5.19.y PATCH 3/3] Smack: Provide read control for io_uring_cmd Paul Moore
2022-09-06 21:25 ` Casey Schaufler
2022-09-11 11:36 ` [v5.19.y PATCH 0/3] Backport the io_uring/LSM CMD passthrough controls Greg KH
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=166249766105.409408.12118839467847524983.stgit@olly \
--to=paul@paul-moore.com \
--cc=axboe@kernel.dk \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=selinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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