tracing: Move d_max_latency out of CONFIG_FSNOTIFY protection

PATCH Superseded Steven Rostedt 1 participant 1 message Feb 10 Tracing

lore

Share & tools

lore

Steven Rostedt

author maintainer

2026-02-10 00:27 UTC #0 lore raw

PATCH 1/1 tracing: Move d_max_latency out of CONFIG_FSNOTIFY protection

From: Steven Rostedt <[email protected]>

The tracing_max_latency shouldn't be limited if CONFIG_FSNOTIFY is defined or not and it was moved out of that protection to be always available with CONFIG_TRACER_MAX_TRACE. All was moved out except the dentry descriptor for it (d_max_latency) and it failed to build on some configs.

Move that out of the CONFIG_FSNOTIFY protection too.

Fixes ba73713da50e ("tracing: Clean up use of trace_create_maxlat_file()")

Reported-by kernel test robot <[email protected]>

Closes https://lore.kernel.org/oe-kbuild-all/[email protected]/ open here

Signed-off-by Steven Rostedt (Google) <[email protected]>

---
 kernel/trace/trace.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

kernel/trace/trace.h +1 -1

index 31fb137e1c66..c08edaa7d179 100644
@@ -346,8 +346,8 @@ struct trace_array {
 	spinlock_t		snapshot_trigger_lock;
 	unsigned int		snapshot;
 	unsigned long		max_latency;
-#ifdef CONFIG_FSNOTIFY
 	struct dentry		*d_max_latency;
+#ifdef CONFIG_FSNOTIFY
 	struct work_struct	fsnotify_work;
 	struct irq_work		fsnotify_irqwork;
 #endif

Signature · 1 line

2.51.0