From: Jeff Layton <jlayton@kernel.org>
To: ChenXiaoSong <chenxiaosong@chenxiaosong.com>,
chuck.lever@oracle.com, neilb@suse.de, okorniev@redhat.com,
Dai.Ngo@oracle.com, tom@talpey.com
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
huhai@kylinos.cn, ChenXiaoSong <chenxiaosong@kylinos.cn>
Subject: Re: [RFC PATCH] nfsd: convert the nfsd_users to atomic_t
Date: Thu, 19 Jun 2025 13:24:50 -0400 [thread overview]
Message-ID: <1ee0e9fa2755f4ed58bd633a71f7632191338a48.camel@kernel.org> (raw)
In-Reply-To: <16608EA06321C225+af69d39b-61e7-4e9a-b382-ecf1e7f2d519@chenxiaosong.com>
On Thu, 2025-06-19 at 15:10 +0800, ChenXiaoSong wrote:
> Yes, nfsd_users is protected by the nfsd_mutex. But the following log
> confuse me, why were they printed in a very short period when crash?
>
> [24225.575708] nfsd: last server has exited, flushing export cache
> [24225.580242] NFSD: starting 90-second grace period (net f0000030)
> ...
> [24225.807458] NFSD: starting 90-second grace period (net f0000030)
>
> Why was callback_wq queued that it had already been freed? And a new
> callback_wq was created. I’ve added some new vmcore analysis to the link:
>
> https://chenxiaosong.com/en/nfs/en-null-ptr-deref-in-nfsd4_probe_callback.html
>
>
> 在 2025/6/18 19:50, Jeff Layton 写道:
> > Isn't nfsd_users protected by the nfsd_mutex? It looks like it's held
> > in all of the places this counter is accessed.
> >
>
I don't know, specifically.
4.19.90 was released more than 5 years ago, and I have no idea what
else you have in that kernel. If this is only reproducible there, then
there's not much we can do to help you. Can you reproduce this on
something more recent?
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-06-19 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 10:41 chenxiaosong
2025-06-18 11:50 ` Jeff Layton
2025-06-19 7:10 ` ChenXiaoSong
2025-06-19 17:24 ` Jeff Layton [this message]
2025-06-20 11:55 ` NeilBrown
2025-06-23 8:52 ` ChenXiaoSong
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=1ee0e9fa2755f4ed58bd633a71f7632191338a48.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=chenxiaosong@kylinos.cn \
--cc=chuck.lever@oracle.com \
--cc=huhai@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/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®