From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Moore <paul@paul-moore.com>
Cc: stable@vger.kernel.org, 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: Re: [v5.19.y PATCH 0/3] Backport the io_uring/LSM CMD passthrough controls
Date: Sun, 11 Sep 2022 13:36:16 +0200 [thread overview]
Message-ID: <Yx3IMBh7gBcDPyx2@kroah.com> (raw)
In-Reply-To: <166249766105.409408.12118839467847524983.stgit@olly>
On Tue, Sep 06, 2022 at 05:03:36PM -0400, Paul Moore wrote:
> 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
>
Now queued up, thanks. Note, you dropped the original signed-off-by of
the original commits, which I had to add back by hand :(
greg k-h
prev parent reply other threads:[~2022-09-11 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 21:03 [v5.19.y PATCH 0/3] Backport the io_uring/LSM CMD passthrough controls Paul Moore
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 ` Greg KH [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=Yx3IMBh7gBcDPyx2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=paul@paul-moore.com \
--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