From: Greg KH <greg@kroah.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: linux-stable <stable@vger.kernel.org>,
Chuck Lever <cel@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 0/3] Fix RELEASE_LOCKOWNER
Date: Fri, 2 Feb 2024 17:04:43 -0800 [thread overview]
Message-ID: <2024020226-aviation-enviably-2f87@gregkh> (raw)
In-Reply-To: <FF7C90E0-251D-48D2-908B-E2145B0B9BAE@oracle.com>
On Fri, Feb 02, 2024 at 02:12:11PM +0000, Chuck Lever III wrote:
>
>
> > On Feb 1, 2024, at 5:24 PM, NeilBrown <neilb@suse.de> wrote:
> >
> > On Fri, 02 Feb 2024, Chuck Lever wrote:
> >> Passes pynfs, fstests, and the git regression suite. Please apply
> >> these to origin/linux-5.4.y.
> >
> > I should have mentioned this a day or two ago but I hadn't quite made
> > all the connection yet...
> >
> > The RELEASE_LOCKOWNER bug was masking a double-free bug that was fixed
> > by
> > Commit 47446d74f170 ("nfsd4: add refcount for nfsd4_blocked_lock")
> > which landed in v5.17 and wasn't marked as a bugfix, and so has not gone to
> > stable kernels.
>
> Then, instructions to stable@vger.kernel.org:
>
> Do not apply the patches I just sent for 5.15, 5.10, and 5.4. I will
> apply 47446d74f170, run the tests again, and resend.
Thanks for letting us know, I've dropped them from my review queue.
greg k-h
next prev parent reply other threads:[~2024-02-03 1:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 19:06 [PATCH 0/3] Fix RELEASE_LOCKOWNER Chuck Lever
2024-02-01 19:06 ` [PATCH 1/3] NFSD: Modernize nfsd4_release_lockowner() Chuck Lever
2024-02-01 19:06 ` [PATCH 2/3] NFSD: Add documenting comment for nfsd4_release_lockowner() Chuck Lever
2024-02-01 19:06 ` [PATCH 3/3] nfsd: fix RELEASE_LOCKOWNER Chuck Lever
2024-02-01 22:24 ` [PATCH 0/3] Fix RELEASE_LOCKOWNER NeilBrown
2024-02-02 14:12 ` Chuck Lever III
2024-02-03 0:26 ` NeilBrown
2024-02-03 3:43 ` Chuck Lever III
2024-02-03 1:04 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 14:23 Chuck Lever
2024-02-01 14:21 Chuck Lever
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=2024020226-aviation-enviably-2f87@gregkh \
--to=greg@kroah.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).