mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vincent Donnefort <vdonnefort@google.com>,
	David Carlier <devnexen@gmail.com>
Subject: [GIT PULL] ring-buffer: Updates for v7.4
Date: Thu, 22 Oct 2026 16:18:02 -0400	[thread overview]
Message-ID: <20261022161802.6d512bac@gandalf.local.home> (raw)


Linus,

ring-buffer updates for v7.4:

- Add Vincent Donnefort as ring-buffer maintainer

  Vincent has been doing a lot of updates to the ftrace ring buffer lately.
  I'm going to start delegating updates for the ring buffer to him.

- Use RING_BUFFER_MIN_NR_PAGES instead of open coding the number 2

  Instead of using the number 2 as the minimum number of pages that a ring
  buffer may have, create and use a macro RING_BUFFER_MIN_NR_PAGES.

- Clean up the resize_disabled_checks

  There's duplication of code to check for resize disabled. Create a helper
  function rb_resize_disabled() and use that. Not only does it put the code
  in one place, it also removed a redundant check.

- Remove unnecessary cpumask_test_cpu checks

  The loop for_each_buffer_cpu(buffer, cpu) only loops over CPUs in the
  buffer->cpumask. There's no reason to test if the CPU is set in that same
  loop.

- Take cpus_read_lock() when changing the subbuf order

  A CPU coming on line for the first time allocates its CPU buffer. But
  if this happens while the subbuffer is being resized, it can cause an
  inconsistent state of subbufer sizes in the buffer. Add a cpus_read_lock()
  to ring_buffer_subbuf_order_set() to prevent this race.


Please pull the latest trace-ringbuffer-v7.4 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace-ringbuffer-v7.4

Tag SHA1: 7e59f123fcd352799b04cc706463f8db0fbfd86e
Head SHA1: 453d0f47b174cac387af48d303c503b84f82212e


David Carlier (1):
      ring-buffer: Take cpus_read_lock() when changing the subbuf order

Steven Rostedt (1):
      ring-buffer: Add a MAINTAINERS category specific for the tracing ring-buffer

Vincent Donnefort (3):
      ring-buffer: Unify ring buffer minimum page calculations
      ring-buffer: Clean up resize_disabled checks
      ring-buffer: Remove unnecessary cpumask_test_cpu

----
 MAINTAINERS                       |  16 ++++++
 include/linux/ring_buffer.h       |   9 +++-
 kernel/trace/ring_buffer.c        | 102 ++++++++++++++++----------------------
 kernel/trace/simple_ring_buffer.c |   4 +-
 4 files changed, 68 insertions(+), 63 deletions(-)
---------------------------

             reply	other threads:[~2026-10-22 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 20:18 Steven Rostedt [this message]
2026-10-23 22:26 ` pr-tracker-bot

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=20261022161802.6d512bac@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=devnexen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vdonnefort@google.com \
    /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®