public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/3] tracing: More fixes for 7.0
Date: Sat, 07 Mar 2026 10:12:24 -0500	[thread overview]
Message-ID: <20260307151224.447677123@kernel.org> (raw)

tracing fixes for 7.0:

- Fix possible NULL pointer dereference in trace_data_alloc()

  On the error path in trace_data_alloc(), it can call trigger_data_free()
  with a NULL pointer. This use to be a kfree() but was changed to
  trigger_data_free() to clean up any partial initialization. The issue is
  that trigger_data_free() does not expect a NULL pointer. Have
  trigger_data_free() return safely on NULL pointer.

- Fix multiple events on the command line and bootconfig

  If multiple events are enabled on the command line separately and not
  grouped, only the last event gets enabled. That is:

    trace_event=sched_switch trace_event=sched_waking

  Will only enable sched_waking where as:

    trace_event=sched_switch,sched_waking

  Will enable both.

  The bootconfig makes it even worse as the second way is the more common
  method.

  The issue is that a temporary buffer is used to store the events to enable
  later in boot. Each time the cmdline callback is called, it overwrites
  what was previously there.

  Have the callback append the next value (delimited by a comma) if the
  temporary buffer already has content.

- Fix command line trace_buffer_size if >= 2G

  The logic to allocate the trace buffer uses "int" for the size parameter
  in the command line code causing overflow issues if more that 2G is
  specified.

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/fixes

Head SHA1: d008ba8be8984760e36d7dcd4adbd5a41a645708


Andrei-Alexandru Tachici (1):
      tracing: Fix enabling multiple events on the kernel command line and bootconfig

Calvin Owens (1):
      tracing: Fix trace_buf_size= cmdline parameter with sizes >= 2G

Guenter Roeck (1):
      tracing: Add NULL pointer check to trigger_data_free()

----
 kernel/trace/trace.c                | 6 +++---
 kernel/trace/trace_events.c         | 6 +++++-
 kernel/trace/trace_events_trigger.c | 3 +++
 3 files changed, 11 insertions(+), 4 deletions(-)

             reply	other threads:[~2026-03-07 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 15:12 Steven Rostedt [this message]
2026-03-07 15:12 ` [for-linus][PATCH 1/3] tracing: Add NULL pointer check to trigger_data_free() Steven Rostedt
2026-03-07 15:12 ` [for-linus][PATCH 2/3] tracing: Fix enabling multiple events on the kernel command line and bootconfig Steven Rostedt
2026-03-07 15:12 ` [for-linus][PATCH 3/3] tracing: Fix trace_buf_size= cmdline parameter with sizes >= 2G 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=20260307151224.447677123@kernel.org \
    --to=rostedt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.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