linux-kernel - Re: [PATCH] tracing: make tr->d_max_latency accessible without CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260211131513.0278b1b3@fedora>
Date: Wed, 11 Feb 2026 13:15:13 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Masami Hiramatsu <mhiramat@...nel.org>, Arnd Bergmann <arnd@...db.de>,
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Tom Zanussi
 <zanussi@...nel.org>, pengdonglin <pengdonglin@...omi.com>, Shengming Hu
 <hu.shengming@....com.cn>, linux-kernel@...r.kernel.org,
 linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: make tr->d_max_latency accessible without
 CONFIG_FSNOTIFY

On Wed, 11 Feb 2026 12:51:52 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Tue, 10 Feb 2026 15:13:06 +0100
> Arnd Bergmann <arnd@...nel.org> wrote:
> 
> > From: Arnd Bergmann <arnd@...db.de>
> > 
> > A recent change attempted to make the tracing_max_latency file visible
> > unconditionally, but this lead to a build failure:
> > 
> > kernel/trace/trace.c: In function 'trace_create_maxlat_file':
> > kernel/trace/trace.c:1543:13: error: 'struct trace_array' has no member named 'd_max_latency'; did you mean 'max_latency'?
> >  1543 |         tr->d_max_latency = trace_create_file("tracing_max_latency",
> >       |             ^~~~~~~~~~~~~
> > 
> > Make the corresponding change in the header file.
> > 
> > Fixes: ba73713da50e ("tracing: Clean up use of trace_create_maxlat_file()")
> > Signed-off-by: Arnd Bergmann <arnd@...db.de>  
> 
> Beat you to it ;-)
> 
>  https://lore.kernel.org/linux-trace-kernel/20260209194631.788bfc85@fedora/

In fact, our changes were so identical that patchwork set both my patch
and your patch to queued when I applied mine to linux-next!

  https://patchwork.kernel.org/project/linux-trace-kernel/patch/20260210141310.1605322-1-arnd@kernel.org/

-- Steve