Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <74076faddd6a92de8c293aad317860a65f8a779a.camel@kernel.org>
Subject: Re: [PATCH 1/1] NFSD: fix use-after-free in __nfs42_ssc_open()
From:   Jeff Layton <jlayton@kernel.org>
To:     Greg KH <greg@kroah.com>, Xingyuan Mo <hdthky0@gmail.com>
Cc:     Dai Ngo <dai.ngo@oracle.com>, chuck.lever@oracle.com,
        kolga@netapp.com, linux-nfs@vger.kernel.org, security@kernel.org
Date:   Mon, 12 Dec 2022 07:26:27 -0500
In-Reply-To: <Y5cXkyWUVf433sd5@kroah.com>
References: <1670786549-27041-1-git-send-email-dai.ngo@oracle.com>
         <CALV6CNOO-Ppv7QfqHo9RKivv-1NUrezbuYN2krrNu4REuchtMA@mail.gmail.com>
         <Y5cXkyWUVf433sd5@kroah.com>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.2 (3.46.2-1.fc37) 
MIME-Version: 1.0
Precedence: bulk

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?
>=20
> 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.
>=20
> 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.
>=20

I think that ship has sailed, as the linux-nfs list was cc'ed on this
patch.
--=20
Jeff Layton <jlayton@kernel.org>