[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250612224059.39fddd07@batman.local.home>
Date: Thu, 12 Jun 2025 22:40:59 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: LKML <linux-kernel@...r.kernel.org>
Cc: Kent Overstreet <kent.overstreet@...ux.dev>,
linux-bcachefs@...r.kernel.org
Subject: Unused trace events in bcachefs
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 for
bcachefs:
warning: tracepoint 'trans_restart_journal_preres_get' is unused.
warning: tracepoint 'trans_restart_fault_inject' is unused.
warning: tracepoint 'trans_restart_relock_after_fill' is unused.
warning: tracepoint 'trans_restart_key_cache_upgrade' is unused.
warning: tracepoint 'trans_restart_relock_key_cache_fill' is unused.
warning: tracepoint 'trans_restart_traverse' is unused.
warning: tracepoint 'trans_restart_key_cache_key_realloced' is unused.
warning: tracepoint 'trans_restart_write_buffer_flush' is unused.
warning: tracepoint 'btree_path_free_trans_begin' is unused.
Each trace event can take up to around 5K in memory regardless if they
are used or not. Soon there will be warnings when they are defined but
not used. Please remove any unused trace event or at least hide it
under an #ifdef if they are used within configs. I'm planning on adding
these warning in the next merge window.
Thanks,
-- Steve
[1] https://lore.kernel.org/linux-trace-kernel/20250612235827.011358765@goodmis.org/
Powered by blists - more mailing lists