From: Anna Schumaker <anna@kernel.org>
To: linux-nfs@vger.kernel.org, trond.myklebust@hammerspace.com
Cc: anna@kernel.org
Subject: [PATCH 0/4] SUNRPC: Various RCU fixes
Date: Fri, 1 Dec 2023 16:15:45 -0500 [thread overview]
Message-ID: <20231201211549.126941-1-anna@kernel.org> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
These are various fixes that I found after turning on CONFIG_LOCKDEP,
CONFIG_PROVE_RCU, and CONFIG_DEBUG_ATOMIC_SLEEP. I didn't hit any issues
when testing against a Linux server, but running against Netapp with pNFS
had several different lockdep & rcu related spews show up in my dmesg
(and that's just from running cthon, not even xfstests). These patches fix
all the issues that I found, and have a couple extra cleanups that I noticed
along the way.
Thoughts?
Anna
Anna Schumaker (4):
SUNRPC: Clean up unused variable in rpc_xprt_probe_trunked()
SUNRPC: Remove unused function rpc_clnt_xprt_switch_put()
SUNRPC: Create a helper function for accessing the rpc_clnt's
xprt_switch
SUNRPC: Fix a suspicious RCU usage warning
include/linux/sunrpc/clnt.h | 1 -
include/linux/sunrpc/xprtmultipath.h | 2 ++
net/sunrpc/clnt.c | 47 +++++++++++++---------------
net/sunrpc/xprtmultipath.c | 14 ++++++++-
4 files changed, 37 insertions(+), 27 deletions(-)
--
2.43.0
next reply other threads:[~2023-12-01 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 21:15 Anna Schumaker [this message]
2023-12-01 21:15 ` [PATCH 1/4] SUNRPC: Clean up unused variable in rpc_xprt_probe_trunked() Anna Schumaker
2023-12-03 12:18 ` Jeff Layton
2023-12-01 21:15 ` [PATCH 2/4] SUNRPC: Remove unused function rpc_clnt_xprt_switch_put() Anna Schumaker
2023-12-03 12:19 ` Jeff Layton
2023-12-01 21:15 ` [PATCH 3/4] SUNRPC: Create a helper function for accessing the rpc_clnt's xprt_switch Anna Schumaker
2023-12-03 12:24 ` Jeff Layton
2023-12-01 21:15 ` [PATCH 4/4] SUNRPC: Fix a suspicious RCU usage warning Anna Schumaker
2023-12-03 12:30 ` Jeff Layton
2023-12-04 17:00 ` Anna Schumaker
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=20231201211549.126941-1-anna@kernel.org \
--to=anna@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.