Commit b4bade50 authored by Steven Rostedt's avatar Steven Rostedt Committed by Steven Rostedt (Google)
Browse files

tracing: Move d_max_latency out of CONFIG_FSNOTIFY protection

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: ba73713d ("tracing: Clean up use of trace_create_maxlat_file()")
Reported-by: default avatarkernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202602092133.fTdojd95-lkp@intel.com/


Signed-off-by: default avatarSteven Rostedt (Google) <rostedt@goodmis.org>
parent c4f1fe47
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -348,8 +348,8 @@ struct trace_array {
	unsigned int		snapshot;
#ifdef CONFIG_TRACER_MAX_TRACE
	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 /* CONFIG_FSNOTIFY */