linux-kernel - Re: [GIT PULL] tracing: Updates for v6.14

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20250120124524.2ed6fdf7@gandalf.local.home>
Date: Mon, 20 Jan 2025 12:45:24 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Masami Hiramatsu
 <mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
 Alice Ryhl <aliceryhl@...gle.com>
Subject: Re: [GIT PULL] tracing: Updates for v6.14

On Sun, 19 Jan 2025 19:29:02 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> - Add :mod: command to enable events for current or future modules
> 
>   The function tracer already has a way to enable functions to be traced in
>   modules by writing ":mod:<module>" into set_ftrace_filter. That will
>   enable either all the functions for the module if it is loaded, or if it
>   is not, it will cache that command, and when the module is loaded that
>   matches <module>, its functions will be enabled. This also allows init
>   functions to be traced. But currently events do not have that feature.
> 
>   Add the command where if ':mod:<module>' is written into set_event, then
>   either all the modules events are enabled if it is loaded, or cache it so
>   that the module's events are enabled when it is loaded. This also works
>   from the kernel command line, where "trace_event=:mod:<module>", when the
>   module is loaded at boot up, its events will be enabled then.

This change added a "#if CONFIG_MODULES" when it should have been a
"#ifdef CONFIG_MODULES". The kernel robot reported this over a week ago and
I fixed it locally, but got distracted and never sent out the fix nor
tested nor applied it.

I'm doing that now, so you can hold off on this pull request.

Thanks,

-- Steve