From: Vincent Donnefort <vdonnefort@google.com>
To: David Carlier <devnexen@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tracing: Fix nr_subbufs initialization in simple_ring_buffer_init_mm()
Date: Tue, 12 May 2026 14:26:38 +0100 [thread overview]
Message-ID: <agMqjjUHD6ZW75dS@google.com> (raw)
In-Reply-To: <20260319094126.109691-1-devnexen@gmail.com>
On Thu, Mar 19, 2026 at 09:41:26AM +0000, David Carlier wrote:
> nr_subbufs in the ring buffer metadata is always initialized to zero
> because it is assigned from cpu_buffer->nr_pages before the page
> initialization loop has run. While nr_subbufs is not currently read
> by the kernel, it should reflect the actual buffer geometry in the
> meta page for correctness.
>
> Move the assignment after the page loop so that cpu_buffer->nr_pages
> holds the final count. Bug discover by Opus AI agent.
nit: I believe we can put that new Assisted-by: tag now.
>
> Fixes: 34e5b958bdad ("tracing: Introduce simple_ring_buffer")
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> kernel/trace/simple_ring_buffer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/simple_ring_buffer.c b/kernel/trace/simple_ring_buffer.c
> index 02af2297ae5a..f731f14d0ff7 100644
> --- a/kernel/trace/simple_ring_buffer.c
> +++ b/kernel/trace/simple_ring_buffer.c
> @@ -395,7 +395,6 @@ int simple_ring_buffer_init_mm(struct simple_rb_per_cpu *cpu_buffer,
>
> memset(cpu_buffer->meta, 0, sizeof(*cpu_buffer->meta));
> cpu_buffer->meta->meta_page_size = PAGE_SIZE;
> - cpu_buffer->meta->nr_subbufs = cpu_buffer->nr_pages;
>
> /* The reader page is not part of the ring initially */
> page = load_page(desc->page_va[0]);
> @@ -437,6 +436,7 @@ int simple_ring_buffer_init_mm(struct simple_rb_per_cpu *cpu_buffer,
> return ret;
> }
>
> + cpu_buffer->meta->nr_subbufs = cpu_buffer->nr_pages;
> /* Close the ring */
> bpage->link.next = &cpu_buffer->tail_page->link;
> cpu_buffer->tail_page->link.prev = &bpage->link;
> --
> 2.53.0
>
Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
parent reply other threads:[~2026-05-12 13:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260319094126.109691-1-devnexen@gmail.com>]
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=agMqjjUHD6ZW75dS@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=ryan.roberts@arm.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