Linux NFS development
 help / color / mirror / Atom feed
* Unused trace events in nfs and nfsd
@ 2025-06-13  1:58 Steven Rostedt
  2025-06-13 15:57 ` Chuck Lever
  0 siblings, 1 reply; 2+ messages in thread
From: Steven Rostedt @ 2025-06-13  1:58 UTC (permalink / raw)
  To: LKML, linux-nfs; +Cc: Chuck Lever, Trond Myklebust, NeilBrown, Jeff Layton

I have code that will trigger a warning if a trace event is defined but
not used[1]. It gives a list of unused events. Here's what I have in nfs
and nfsd:

warning: tracepoint 'nfs4_renew' is unused.
warning: tracepoint 'nfs4_rename' is unused.
warning: tracepoint 'nfsd_file_unhash_and_queue' is unused.
warning: tracepoint 'nfsd_file_lru_add_disposed' is unused.
warning: tracepoint 'nfsd_file_lru_del_disposed' is unused.
warning: tracepoint 'nfsd_file_gc_recent' is unused.
warning: tracepoint 'nfsd_ctl_maxconn' is unused.

nfs4_renew looks to never have been used.

trace_nfs4_rename() was removed by 33912be816d9 ("nfs: remove
synchronous rename code") but did not remove the event.

trace_nfsd_file_unhash_and_queue() was removed by ac3a2585f01 ("nfsd:
rework refcounting in filecache")

Events nfsd_file_lru_add_disposed and nfsd_file_lru_del_disposed were
added by 4a0e73e635e3 ("NFSD: Leave open files out of the filecache
LRU") but they were never used.

Event nfsd_file_gc_recent was added by 64912122a4f8 ("nfsd: filecache:
introduce NFSD_FILE_RECENT") but never used.

trace_nfsd_ctl_maxconn() was removed by a4b853f183a1 ("sunrpc: remove
all connection limit configuration") but did not remove the event.

-- Steve

[1] https://lore.kernel.org/linux-trace-kernel/20250612235827.011358765@goodmis.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Unused trace events in nfs and nfsd
  2025-06-13  1:58 Unused trace events in nfs and nfsd Steven Rostedt
@ 2025-06-13 15:57 ` Chuck Lever
  0 siblings, 0 replies; 2+ messages in thread
From: Chuck Lever @ 2025-06-13 15:57 UTC (permalink / raw)
  To: Steven Rostedt, LKML, linux-nfs; +Cc: Trond Myklebust, NeilBrown, Jeff Layton

On 6/12/25 9:58 PM, Steven Rostedt wrote:
> I have code that will trigger a warning if a trace event is defined but
> not used[1]. It gives a list of unused events. Here's what I have in nfs
> and nfsd:
> 
> warning: tracepoint 'nfs4_renew' is unused.
> warning: tracepoint 'nfs4_rename' is unused.
> warning: tracepoint 'nfsd_file_unhash_and_queue' is unused.
> warning: tracepoint 'nfsd_file_lru_add_disposed' is unused.
> warning: tracepoint 'nfsd_file_lru_del_disposed' is unused.
> warning: tracepoint 'nfsd_file_gc_recent' is unused.
> warning: tracepoint 'nfsd_ctl_maxconn' is unused.
> 
> nfs4_renew looks to never have been used.
> 
> trace_nfs4_rename() was removed by 33912be816d9 ("nfs: remove
> synchronous rename code") but did not remove the event.
> 
> trace_nfsd_file_unhash_and_queue() was removed by ac3a2585f01 ("nfsd:
> rework refcounting in filecache")
> 
> Events nfsd_file_lru_add_disposed and nfsd_file_lru_del_disposed were
> added by 4a0e73e635e3 ("NFSD: Leave open files out of the filecache
> LRU") but they were never used.
> 
> Event nfsd_file_gc_recent was added by 64912122a4f8 ("nfsd: filecache:
> introduce NFSD_FILE_RECENT") but never used.
> 
> trace_nfsd_ctl_maxconn() was removed by a4b853f183a1 ("sunrpc: remove
> all connection limit configuration") but did not remove the event.
> 
> -- Steve
> 
> [1] https://lore.kernel.org/linux-trace-kernel/20250612235827.011358765@goodmis.org/

Thanks for the report. I'll clean up the NFSD-related tracepoints for
the v6.17 merge window.


-- 
Chuck Lever

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-06-13 15:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-13  1:58 Unused trace events in nfs and nfsd Steven Rostedt
2025-06-13 15:57 ` Chuck Lever

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox