From: Greg KH <greg@kroah.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Xingyuan Mo <hdthky0@gmail.com>, Dai Ngo <dai.ngo@oracle.com>,
chuck.lever@oracle.com, kolga@netapp.com,
linux-nfs@vger.kernel.org, security@kernel.org
Subject: Re: [PATCH 1/1] NFSD: fix use-after-free in __nfs42_ssc_open()
Date: Mon, 12 Dec 2022 13:44:45 +0100 [thread overview]
Message-ID: <Y5ciPU5rNaukLUB7@kroah.com> (raw)
In-Reply-To: <74076faddd6a92de8c293aad317860a65f8a779a.camel@kernel.org>
On Mon, Dec 12, 2022 at 07:26:27AM -0500, Jeff Layton wrote:
> On Mon, 2022-12-12 at 12:59 +0100, Greg KH wrote:
> > On Mon, Dec 12, 2022 at 07:22:38PM +0800, Xingyuan Mo wrote:
> > > Can I share the patch with the linux-distros list, so that
> > > distros can do their own testing and preparations?
> >
> > Be _VERY_ aware of the rules regarding that list before you send
> > anything as you are going to have some very strict rules put on you with
> > regards to what you must do once you post to them.
> >
> > Personally, I would prefer if this gets into Linus's tree first so that
> > we can get it into a stable release before letting distros know about
> > it, otherwise you are forcing me into a very tight schedule that might
> > require you to tell the world about the problem _BEFORE_ the fix is in
> > Linus's or any stable kernel trees.
> >
>
> I think that ship has sailed, as the linux-nfs list was cc'ed on this
> patch.
Ah, missed that, nice!
So no need to let linux-distros know about it either :)
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-12 12:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 19:22 [PATCH 1/1] NFSD: fix use-after-free in __nfs42_ssc_open() Dai Ngo
2022-12-12 11:22 ` Xingyuan Mo
2022-12-12 11:59 ` Greg KH
2022-12-12 12:26 ` Jeff Layton
2022-12-12 12:44 ` Greg KH [this message]
2022-12-12 13:44 ` Xingyuan Mo
2022-12-12 12:22 ` Jeff Layton
2022-12-12 13:34 ` dai.ngo
2022-12-12 13:40 ` Jeff Layton
2022-12-12 13:57 ` dai.ngo
2022-12-12 13:59 ` Greg KH
2022-12-12 14:31 ` Jeff Layton
2022-12-12 17:14 ` Greg KH
2022-12-12 17:44 ` Jeff Layton
2022-12-12 18:16 ` Chuck Lever III
2022-12-12 18:38 ` Jeff Layton
2022-12-12 19:16 ` dai.ngo
2022-12-12 19:28 ` Chuck Lever III
2022-12-12 19:45 ` dai.ngo
2022-12-12 19:46 ` Jeff Layton
2022-12-12 19:48 ` Chuck Lever III
2022-12-12 19:59 ` dai.ngo
2022-12-12 21:17 ` Jeff Layton
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=Y5ciPU5rNaukLUB7@kroah.com \
--to=greg@kroah.com \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=hdthky0@gmail.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=security@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