From: Lorenzo Bianconi <lorenzo@kernel.org>
To: linux-nfs@vger.kernel.org
Cc: lorenzo.bianconi@redhat.com, chuck.lever@oracle.com,
jlayton@kernel.org, neilb@suse.de
Subject: [PATCH v4 0/2] add rpc_status handler in nfsd debug filesystem
Date: Fri, 28 Jul 2023 20:44:02 +0200 [thread overview]
Message-ID: <cover.1690569488.git.lorenzo@kernel.org> (raw)
Introduce rpc_status entry in nfsd debug filesystem in order to dump
pending RPC requests debugging information.
Changes since v3:
- introduce rq_status_counter in order to detect if the RPC request is
pending and RPC info are stable
- rely on __svc_print_addr to dump IP info
Changes since v2:
- minor changes in nfsd_rpc_status_show output
Changes since v1:
- rework nfsd_rpc_status_show output
Changes since RFCv1:
- riduce time holding nfsd_mutex bumping svc_serv refcoung in
nfsd_rpc_status_open()
- dump rqstp->rq_stime
- add missing kdoc for nfsd_rpc_status_open()
Link: https://bugzilla.linux-nfs.org/show_bug.cgi?id=366
Lorenzo Bianconi (2):
SUNRPC: add verbose parameter to __svc_print_addr()
NFSD: add rpc_status entry in nfsd debug filesystem
fs/nfsd/nfs4proc.c | 4 +-
fs/nfsd/nfsctl.c | 10 +++
fs/nfsd/nfsd.h | 2 +
fs/nfsd/nfssvc.c | 122 ++++++++++++++++++++++++++++++++
include/linux/sunrpc/svc.h | 1 +
include/linux/sunrpc/svc_xprt.h | 12 ++--
net/sunrpc/svc.c | 2 +-
net/sunrpc/svc_xprt.c | 2 +-
8 files changed, 144 insertions(+), 11 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-28 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 18:44 Lorenzo Bianconi [this message]
2023-07-28 18:44 ` [PATCH v4 1/2] SUNRPC: add verbose parameter to __svc_print_addr() Lorenzo Bianconi
2023-07-28 22:13 ` NeilBrown
2023-07-31 16:11 ` Jeff Layton
2023-07-31 22:15 ` NeilBrown
2023-07-28 18:44 ` [PATCH v4 2/2] NFSD: add rpc_status entry in nfsd debug filesystem Lorenzo Bianconi
2023-07-28 19:22 ` Chuck Lever
2023-07-28 22:11 ` NeilBrown
2023-08-04 8:02 ` Lorenzo Bianconi
2023-08-04 7:56 ` Lorenzo Bianconi
2023-08-04 14:02 ` Chuck Lever
2023-07-28 22:23 ` NeilBrown
2023-08-02 8:58 ` Lorenzo Bianconi
2023-07-29 5:18 ` kernel test robot
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=cover.1690569488.git.lorenzo@kernel.org \
--to=lorenzo@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=neilb@suse.de \
/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