linux-kernel - Re: [GIT PULL] tracing: Fix trace event check for 6.13

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: <Z3P7CD5y5Wz7QeOM@lappy>
Date: Tue, 31 Dec 2024 09:09:12 -0500
From: Sasha Levin <sashal@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Masami Hiramatsu <mhiramat@...nel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Gene C <arch@...ience.com>
Subject: Re: [GIT PULL] tracing: Fix trace event check for 6.13

On Tue, Dec 31, 2024 at 08:56:22AM -0500, Steven Rostedt wrote:
>
>Linus,
>
>Tracing fix for 6.13:
>
>- Fix trace event string check when dealing with array of strings
>
>  The xe_bo_move event has a field that indexes into an array of
>  strings. The TP_fast_assign() added the index into the ring buffer
>  and the TP_printk() had a "%s" that referenced the array using the
>  index in the ring buffer. This is a legitimate use of "%s" in
>  trace events. But this triggered a false positive in the
>  test_event_printk() at boot saying that the string was dangerous.
>
>  Change the check to allow arrays using fields in the ring buffer
>  as an index to be considered a safe string.
>
>
>Please pull the latest trace-v6.13-rc5 tree, which can be found at:
>
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
>trace-v6.13-rc5

You might have forgotten to push the tag :)

-- 
Thanks,
Sasha