From: Vincent Donnefort <vdonnefort@google.com>
To: David Carlier <devnexen@gmail.com>
Cc: rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] ring-buffer: Take cpus_read_lock() when changing the subbuf order
Date: Thu, 17 Sep 2026 07:55:29 +0100 [thread overview]
Message-ID: <aquO4fKay-7zTBRw@google.com> (raw)
In-Reply-To: <20260916192628.274136-1-devnexen@gmail.com>
On Wed, Sep 16, 2026 at 08:26:28PM +0100, David Carlier wrote:
> A CPU coming online for the first time gets its per CPU buffer allocated
> by trace_rb_cpu_prepare(), which then adds it to buffer->cpumask. If that
> happens while ring_buffer_subbuf_order_set() is running, the CPU shows up
> after the allocation loop and the install loop walks it with an empty
> new_pages list, corrupting the buffer.
>
> Take cpus_read_lock() as ring_buffer_resize() does.
>
> Fixes: f9b94daa542a ("ring-buffer: Set new size of the ring buffer sub page")
> Cc: stable@vger.kernel.org
> Signed-off-by: David Carlier <devnexen@gmail.com>
It is usually good practice to not link the different versions of patches
together.
Beside,
Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
> ---
>
> Notes:
> v2:
> - Reword the changelog: offlined CPUs stay in ->cpumask, so only a CPU
> coming online for the first time can appear mid-flight (Vincent)
> - Drop the comment above guard(cpus_read_lock)() (Vincent)
>
> v1: https://lore.kernel.org/linux-trace-kernel/20260914182850.21449-1-devnexen@gmail.com/
>
> kernel/trace/ring_buffer.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 04bb94c29f58..e78fb4bb2195 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -7464,6 +7464,8 @@ int ring_buffer_subbuf_order_set(struct trace_buffer *buffer, int order)
> if (psize > RB_WRITE_MASK + 1)
> return -EINVAL;
>
> + guard(cpus_read_lock)();
> +
> /* prevent another thread from changing buffer sizes */
> guard(mutex)(&buffer->mutex);
>
> --
> 2.55.0
>
--
Vincent
prev parent reply other threads:[~2026-09-17 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 18:28 [PATCH] " David Carlier
2026-09-15 7:16 ` Vincent Donnefort
2026-09-16 19:26 ` [PATCH v2] " David Carlier
2026-09-17 6:55 ` Vincent Donnefort [this message]
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=aquO4fKay-7zTBRw@google.com \
--to=vdonnefort@google.com \
--cc=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®