public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>,
	 linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] nfs: new tracepoint in match_stateid operation
Date: Tue, 10 Jun 2025 09:09:56 -0400	[thread overview]
Message-ID: <d19d4a507361dad7d0cde2b94f01faf0fb866676.camel@kernel.org> (raw)
In-Reply-To: <9BD9513B-972A-4C83-9100-A11F289191E5@redhat.com>

On Tue, 2025-06-10 at 09:04 -0400, Benjamin Coddington wrote:
> On 3 Jun 2025, at 7:42, Jeff Layton wrote:
> 
> > Add new tracepoints in the NFSv4 match_stateid minorversion op that show
> > the info in both stateids.
> > 
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> >  fs/nfs/nfs4proc.c  |  4 ++++
> >  fs/nfs/nfs4trace.h | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  2 files changed, 60 insertions(+)
> > 
> > diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> > index 341740fa293d8fb1cfabe0813c7fcadf04df4f62..80126290589aaccd801c8965252523894e37c44a 100644
> > --- a/fs/nfs/nfs4proc.c
> > +++ b/fs/nfs/nfs4proc.c
> > @@ -10680,6 +10680,8 @@ nfs41_free_lock_state(struct nfs_server *server, struct nfs4_lock_state *lsp)
> >  static bool nfs41_match_stateid(const nfs4_stateid *s1,
> >  		const nfs4_stateid *s2)
> >  {
> > +	trace_nfs41_match_stateid(s1, s2);
> > +
> >  	if (s1->type != s2->type)
> >  		return false;
> > 
> > @@ -10697,6 +10699,8 @@ static bool nfs41_match_stateid(const nfs4_stateid *s1,
> >  static bool nfs4_match_stateid(const nfs4_stateid *s1,
> >  		const nfs4_stateid *s2)
> >  {
> > +	trace_nfs4_match_stateid(s1, s2);
> > +
> >  	return nfs4_stateid_match(s1, s2);
> >  }
> > 
> > diff --git a/fs/nfs/nfs4trace.h b/fs/nfs/nfs4trace.h
> > index 73a6b60a848066546c2ae98b4982b0ab36bb0f73..9b56ce9f2f3dcb31a3e21d5740bcf62aca814214 100644
> > --- a/fs/nfs/nfs4trace.h
> > +++ b/fs/nfs/nfs4trace.h
> > @@ -1497,6 +1497,62 @@ DECLARE_EVENT_CLASS(nfs4_inode_stateid_callback_event,
> >  DEFINE_NFS4_INODE_STATEID_CALLBACK_EVENT(nfs4_cb_recall);
> >  DEFINE_NFS4_INODE_STATEID_CALLBACK_EVENT(nfs4_cb_layoutrecall_file);
> > 
> > +#define show_stateid_type(type) \
> > +	__print_symbolic(type, \
> > +		{ NFS4_INVALID_STATEID_TYPE, "INVALID" }, \
> > +		{ NFS4_SPECIAL_STATEID_TYPE, "SPECIAL" }, \
> > +		{ NFS4_OPEN_STATEID_TYPE, "OPEN" }, \
> > +		{ NFS4_LOCK_STATEID_TYPE, "LOCK" }, \
> > +		{ NFS4_DELEGATION_STATEID_TYPE, "DELEGATION" }, \
> > +		{ NFS4_LAYOUT_STATEID_TYPE, "LAYOUT" },	\
> > +		{ NFS4_PNFS_DS_STATEID_TYPE, "PNFS_DS" }, \
> > +		{ NFS4_REVOKED_STATEID_TYPE, "REVOKED" })
> 
> Let's add NFS4_FREED_STATEID_TYPE at the end here, for after 77be29b7a3f89.
>
> Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
> 
> Ben

Thanks, good catch. I did these patches a while ago and may have missed
some of the more recent changes. Anna, can you fix that up or would you
rather I resend the set?
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-06-10 13:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 11:42 [PATCH 0/4] nfs: client-side tracepoints for delegations and cache coherency Jeff Layton
2025-06-03 11:42 ` [PATCH 1/4] nfs: add cache_validity to the nfs_inode_event tracepoints Jeff Layton
2025-06-03 11:42 ` [PATCH 2/4] nfs: add a tracepoint to nfs_inode_detach_delegation_locked Jeff Layton
2025-06-03 11:42 ` [PATCH 3/4] nfs: new tracepoint in nfs_delegation_need_return Jeff Layton
2025-06-03 11:42 ` [PATCH 4/4] nfs: new tracepoint in match_stateid operation Jeff Layton
2025-06-10 13:04   ` Benjamin Coddington
2025-06-10 13:09     ` Jeff Layton [this message]
2025-06-17 18:45       ` Trond Myklebust
2025-06-10 13:05 ` [PATCH 0/4] nfs: client-side tracepoints for delegations and cache coherency Benjamin Coddington

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=d19d4a507361dad7d0cde2b94f01faf0fb866676.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=anna@kernel.org \
    --cc=bcodding@redhat.com \
    --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