From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: Paul Moore <paul@paul-moore.com>
Cc: "James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Christian Brauner" <brauner@kernel.org>,
"Dave Chinner" <dchinner@redhat.com>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"John Johansen" <john.johansen@canonical.com>,
"Micah Morton" <mortonm@chromium.org>,
"Günther Noack" <gnoack3000@gmail.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Mickaël Salaün" <mic@digikod.net>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Vivek Goyal" <vgoyal@redhat.com>
Subject: Re: [PATCH] security, lsm: security_old_inode_init_security() Handle multi LSM registration
Date: Wed, 5 Apr 2023 17:30:31 +0200 [thread overview]
Message-ID: <ZC2UF7FfJ1XDEu67@valentin-vidic.from.hr> (raw)
In-Reply-To: <CAHC9VhTCafjmo7k=qGnOMDm4s4UHL9g=o5KgRfg9_xwWCzUhcw@mail.gmail.com>
On Mon, Apr 03, 2023 at 03:28:11PM -0400, Paul Moore wrote:
> I think backporting it to the stable kernels would be okay, but I'd
> prefer to let it get some more testing in linux-next first if that's
> okay with you. Since we are currently at v6.3-rc5 and this patch is
> scheduled to go up to Linus during the next merge window, it might
> make the most sense to give this two more weeks in -next, let it land
> in Linus' tree, and they ask the stable team for a backport ("Option
> 2" in the stable kernel docs):
>
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
> Thoughts?
No problem for me, as long as it gets included in the LTS at some point :)
--
Valentin
prev parent reply other threads:[~2023-04-05 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 21:41 Valentin Vidic
2023-04-02 15:14 ` Paul Moore
2023-04-02 20:03 ` Valentin Vidić
2023-04-03 19:28 ` Paul Moore
2023-04-05 15:30 ` Valentin Vidić [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=ZC2UF7FfJ1XDEu67@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dchinner@redhat.com \
--cc=gnoack3000@gmail.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mortonm@chromium.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=vgoyal@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®