tracing: Move d_max_latency out of CONFIG_FSNOTIFY protection

[ Upstream commit b4bade506b18eb2e5e34ac84f915d7ee6156d4e2 ]

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.

Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Link: https://patch.msgid.link/20260209194631.788bfc85@fedora
Fixes: ba73713da50e ("tracing: Clean up use of trace_create_maxlat_file()")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202602092133.fTdojd95-lkp@intel.com/
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>

diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
index 89e4d619e64b9e93220b155078634432fe234b58..729b1921f955488ce22da60ad5745d4eb79b6fa9 100644 (file)
--- a/kernel/trace/trace.h
+++ b/kernel/trace/trace.h
@@ -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