From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Chris Rankin <rankincj@gmail.com>, Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: [BUG] Linux 6.8.10 NPE
Date: Mon, 20 May 2024 20:11:52 +0800 [thread overview]
Message-ID: <aa0fec0b-b12a-b0b6-2d28-bad69f6034cb@linux.dev> (raw)
In-Reply-To: <CAK2bqVLaki4Jqq67jWcW+fedDYJRk5xrsgNZq5TH4iBTu8AvMg@mail.gmail.com>
On 5/19/24 23:51, Chris Rankin wrote:
> nfsd_show+0x39/0x18e:
>
> net_generic at /home/chris/LINUX/linux-6.8/include/net/netns/generic.h:47
> 42 struct net_generic *ng;
> 43 void *ptr;
> 44
> 45 rcu_read_lock();
> 46 ng = rcu_dereference(net->gen);
>> 47< ptr = ng->ptr[id];
> 48 rcu_read_unlock();
> 49
> 50 return ptr;
> 51 }
> 52 #endif
>
> (inlined by) nfsd_show at /home/chris/LINUX/linux-6.8/fs/nfsd/stats.c:38
> 33 };
> 34
> 35 static int nfsd_show(struct seq_file *seq, void *v)
> 36 {
> 37 struct net *net = pde_data(file_inode(seq->file));
The implementation of pde_data is depend on CONFIG_PROC_FS, maybe nfsd_show
need to check the dependency too just like write_gssp.
>> 38< struct nfsd_net *nn = net_generic(net, nfsd_net_id);
> 39 int i;
> 40
> 41 seq_printf(seq, "rc %lld %lld %lld\nfh %lld 0 0 0 0\nio
> %lld %lld\n",
> 42
> percpu_counter_sum_positive(&nn->counter[NFSD_STATS_RC_HITS]),
> 43
> percpu_counter_sum_positive(&nn->counter[NFSD_STATS_RC_MISSES]),
Thanks,
Guoqing
prev parent reply other threads:[~2024-05-20 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK2bqVJoT3yy2m0OmTnqH9EAKkj6O1iTk42EyyMtvvxKh6YDKg@mail.gmail.com>
2024-05-19 12:26 ` Fwd: [BUG] Linux 6.8.10 NPE Chris Rankin
2024-05-19 13:15 ` Chris Rankin
2024-05-19 14:58 ` Jeff Layton
2024-05-19 15:51 ` Chris Rankin
2024-05-19 17:02 ` Jeff Layton
[not found] ` <CAK2bqV+3J0tQOogDLBNBD0QRkc70L1sR8CqONhAotcDDG8N6AA@mail.gmail.com>
2024-05-19 19:17 ` Chris Rankin
2024-05-20 12:11 ` Guoqing Jiang [this message]
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=aa0fec0b-b12a-b0b6-2d28-bad69f6034cb@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rankincj@gmail.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