From: Sean Chang <seanwascoding@gmail.com>
To: trondmy@kernel.org, anna@kernel.org
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Chang <seanwascoding@gmail.com>
Subject: [PATCH v1 0/2] NFS: fix RCU and tracing pointer safety
Date: Thu, 9 Apr 2026 00:14:26 +0800 [thread overview]
Message-ID: <20260408161428.155169-1-seanwascoding@gmail.com> (raw)
This series addresses two Sparse static analysis warnings in the NFS
client.
The first patch fixes an RCU-unsafe dereference when comparing
superblock addresses by adding the necessary RCU read lock and
dereference wrappers.
The second patch resolves a "noderef" warning in the tracing
infrastructure by changing a pointer field to an unsigned long,
ensuring we aren't incorrectly marking private trace-buffer
pointers as dereferenceable.
Sean Chang (2):
NFS: fix RCU safety in nfs_compare_super_address
NFS: use unsigned long for req field in nfs_page_class
fs/nfs/nfstrace.h | 6 +++---
fs/nfs/super.c | 32 ++++++++++++++++++++++----------
2 files changed, 25 insertions(+), 13 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-08 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 16:14 Sean Chang [this message]
2026-04-08 16:14 ` [PATCH v1 1/2] NFS: fix RCU safety in nfs_compare_super_address Sean Chang
2026-04-08 16:14 ` [PATCH v1 2/2] NFS: use unsigned long for req field in nfs_page_class Sean Chang
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=20260408161428.155169-1-seanwascoding@gmail.com \
--to=seanwascoding@gmail.com \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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