From: "J. Bruce Fields" <bfields@fieldses.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: Kernel panic / list_add corruption when in nfsd4_run_cb_work
Date: Mon, 12 Oct 2020 12:33:55 -0400 [thread overview]
Message-ID: <20201012163355.GF26571@fieldses.org> (raw)
In-Reply-To: <20201012154159.GA49819@eldamar.lan>
On Mon, Oct 12, 2020 at 05:41:59PM +0200, Salvatore Bonaccorso wrote:
> Hi Bruce,
>
> Thanks a lot for your reply, much appreciated.
>
> On Mon, Oct 12, 2020 at 10:26:02AM -0400, J. Bruce Fields wrote:
> > On Sun, Oct 11, 2020 at 09:59:13AM +0200, Salvatore Bonaccorso wrote:
> > > Hi
> > >
> > > On a system running 4.19.146-1 in Debian buster an issue got hit,
> > > while the server was under some slight load, but it does not seem
> > > easily reproducible, so asking if some more information can be
> > > provided to track/narrow this down. On the console the following was
> > > caught:
> >
> > Worth checking git logs of fs/nfsd/nfs4state.c and
> > fs/nfsd/nfs4callback.c. It might be
> > 2bbfed98a4d82ac4e7abfcd4eba40bddfc670b1d "nfsd: Fix races between
> > nfsd4_cb_release() and nfsd4_shutdown_callback()" ?
>
> That might be possible. As it was not possible to simply trigger the
> issue, do you know if it is possible to simply reproduce the issue
> fixed in the above?
I don't have a reproducer.
--b.
>
> 2bbfed98a4d8 ("nfsd: Fix races between nfsd4_cb_release() and
> nfsd4_shutdown_callback()") would be missing in the v4.19.y stable
> series (as it was in 5.5-rc1 but not backported to other stable
> versions).
>
> Regards,
> Salvatore
next prev parent reply other threads:[~2020-10-12 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 7:59 Kernel panic / list_add corruption when in nfsd4_run_cb_work Salvatore Bonaccorso
2020-10-12 14:26 ` J. Bruce Fields
2020-10-12 15:41 ` Salvatore Bonaccorso
2020-10-12 16:33 ` J. Bruce Fields [this message]
2020-10-18 9:39 ` Salvatore Bonaccorso
2021-10-06 18:46 ` Salvatore Bonaccorso
2021-11-22 9:15 ` Olivier Monaco
2021-11-22 15:17 ` Chuck Lever III
2021-11-24 15:29 ` Bruce Fields
2021-11-24 15:59 ` Trond Myklebust
2021-11-24 16:10 ` Trond Myklebust
2021-11-24 16:10 ` bfields
2021-11-24 17:14 ` Trond Myklebust
2021-11-24 22:06 ` bfields
2021-11-24 22:17 ` Trond Myklebust
2021-12-01 22:33 ` bfields
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=20201012163355.GF26571@fieldses.org \
--to=bfields@fieldses.org \
--cc=carnil@debian.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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).