From: Jeff Layton <jlayton@kernel.org>
To: cel@kernel.org, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH] NFSD: Fix trace_nfsd_slot_seqid_sequence
Date: Mon, 03 Feb 2025 10:11:41 -0500 [thread overview]
Message-ID: <9adf2944956561ff70580e85bfbbb093bb73cc9e.camel@kernel.org> (raw)
In-Reply-To: <20250203144942.68547-1-cel@kernel.org>
On Mon, 2025-02-03 at 09:49 -0500, cel@kernel.org wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> While running down the problem triggered by disconnect injection,
> I noticed the "in use" string was actually never hooked up in this
> trace point, so it always showed the traced slot as not in use. But
> what might be more useful is showing all the slot status flags.
>
> Also, this trace point can record and report the slot's index
> number, which among other things is useful for troubleshooting slot
> table expansion and contraction.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> fs/nfsd/trace.h | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/fs/nfsd/trace.h b/fs/nfsd/trace.h
> index ad2c0c432d08..49bbd26ffcdb 100644
> --- a/fs/nfsd/trace.h
> +++ b/fs/nfsd/trace.h
> @@ -803,6 +803,14 @@ DEFINE_EVENT(nfsd_cs_slot_class, nfsd_##name, \
> DEFINE_CS_SLOT_EVENT(slot_seqid_conf);
> DEFINE_CS_SLOT_EVENT(slot_seqid_unconf);
>
> +#define show_nfs_slot_flags(val) \
> + __print_flags(val, "|", \
> + { NFSD4_SLOT_INUSE, "INUSE" }, \
> + { NFSD4_SLOT_CACHETHIS, "CACHETHIS" }, \
> + { NFSD4_SLOT_INITIALIZED, "INITIALIZED" }, \
> + { NFSD4_SLOT_CACHED, "CACHED" }, \
> + { NFSD4_SLOT_REUSED, "REUSED" })
> +
> TRACE_EVENT(nfsd_slot_seqid_sequence,
> TP_PROTO(
> const struct nfs4_client *clp,
> @@ -813,10 +821,11 @@ TRACE_EVENT(nfsd_slot_seqid_sequence,
> TP_STRUCT__entry(
> __field(u32, seqid)
> __field(u32, slot_seqid)
> + __field(u32, slot_index)
> + __field(unsigned long, slot_flags)
> __field(u32, cl_boot)
> __field(u32, cl_id)
> __sockaddr(addr, clp->cl_cb_conn.cb_addrlen)
> - __field(bool, in_use)
> ),
> TP_fast_assign(
> __entry->cl_boot = clp->cl_clientid.cl_boot;
> @@ -825,11 +834,13 @@ TRACE_EVENT(nfsd_slot_seqid_sequence,
> clp->cl_cb_conn.cb_addrlen);
> __entry->seqid = seq->seqid;
> __entry->slot_seqid = slot->sl_seqid;
> + __entry->slot_index = seq->slotid;
> + __entry->slot_flags = slot->sl_flags;
> ),
> - TP_printk("addr=%pISpc client %08x:%08x seqid=%u slot_seqid=%u (%sin use)",
> + TP_printk("addr=%pISpc client %08x:%08x idx=%u seqid=%u slot_seqid=%u flags=%s",
> __get_sockaddr(addr), __entry->cl_boot, __entry->cl_id,
> - __entry->seqid, __entry->slot_seqid,
> - __entry->in_use ? "" : "not "
> + __entry->slot_index, __entry->seqid, __entry->slot_seqid,
> + show_nfs_slot_flags(__entry->slot_flags)
> )
> );
>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-02-03 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 14:49 [PATCH] NFSD: Fix trace_nfsd_slot_seqid_sequence cel
2025-02-03 15:11 ` Jeff Layton [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=9adf2944956561ff70580e85bfbbb093bb73cc9e.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--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