mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Gene C <arch@sapience.com>
Subject: Re: [GIT PULL] tracing: Fix trace event check for 6.13
Date: Tue, 31 Dec 2024 09:09:12 -0500	[thread overview]
Message-ID: <Z3P7CD5y5Wz7QeOM@lappy> (raw)
In-Reply-To: <20241231085622.35f69353@gandalf.local.home>

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

  reply	other threads:[~2024-12-31 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-31 13:56 Steven Rostedt
2024-12-31 14:09 ` Sasha Levin [this message]
2024-12-31 14:16   ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z3P7CD5y5Wz7QeOM@lappy \
    --to=sashal@kernel.org \
    --cc=arch@sapience.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®