All of lore.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/4] tracing: Fixes for v7.2
Date: Fri, 10 Jul 2026 21:20:40 -0400	[thread overview]
Message-ID: <20260711012040.762290323@kernel.org> (raw)

tracing fixes for v7.2:

- Add selftest that tests deferred event teardown

- Fix leak in error path of trace_remote_alloc_buffer()

  If page allocation fails, the desc->nr_cpus is not incremented for the
  current CPU and the allocations done for it are not freed.

- Fix allocation length in trace_remote_alloc_buffer()

  The logic to calculate the struct_len was doing a double count and setting
  the value too large. Calculate the size upfront to fix the error and
  simplify the logic.

- Fix sparse CPU masks in ring_buffer_desc()

  If there are sparse CPUs (gaps in the numbering), the ring_buffer_desc()
  will fail as it tests the CPU number against the number of CPUs that are
  used.

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

Head SHA1: 601ddaceb861be7eb557278109966320a6f3478c


Michael Bommarito (1):
      selftests/user_events: Wait for deferred event teardown after unregister

Vincent Donnefort (3):
      tracing/remotes: Fix leak in trace_remote_alloc_buffer() error path
      tracing/remotes: Fix struct_len in trace_remote_alloc_buffer()
      ring-buffer: Allow sparse CPU masks in ring_buffer_desc()

----
 kernel/trace/ring_buffer.c                      |  5 +----
 kernel/trace/trace_remote.c                     | 18 +++++----------
 tools/testing/selftests/user_events/abi_test.c  | 29 ++++++++++++++++++++++++-
 tools/testing/selftests/user_events/perf_test.c | 26 +++++++++++++++++++---
 4 files changed, 58 insertions(+), 20 deletions(-)

             reply	other threads:[~2026-07-11  1:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  1:20 Steven Rostedt [this message]
2026-07-11  1:20 ` [for-linus][PATCH 1/4] selftests/user_events: Wait for deferred event teardown after unregister Steven Rostedt
2026-07-11  1:20 ` [for-linus][PATCH 2/4] tracing/remotes: Fix leak in trace_remote_alloc_buffer() error path Steven Rostedt
2026-07-11  1:20 ` [for-linus][PATCH 3/4] tracing/remotes: Fix struct_len in trace_remote_alloc_buffer() Steven Rostedt
2026-07-11  1:20 ` [for-linus][PATCH 4/4] ring-buffer: Allow sparse CPU masks in ring_buffer_desc() 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=20260711012040.762290323@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.