Linux Trace Kernel
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, linux-trace-kernel@vger.kernel.org,
	mathieu.desnoyers@efficios.com, kernel-team@android.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] tracing/remotes: Account for ring buffer page header in size calculation
Date: Fri, 11 Sep 2026 15:32:58 +0100	[thread overview]
Message-ID: <aqQRGv26MEjjl1Br@google.com> (raw)
In-Reply-To: <20260909181316.676b8c56@gandalf.local.home>

On Wed, Sep 09, 2026 at 06:13:16PM -0400, Steven Rostedt wrote:
> On Mon,  7 Sep 2026 20:26:42 +0100
> Vincent Donnefort <vdonnefort@google.com> wrote:
> 
> > trace_buffer_desc_size() and trace_remote_alloc_buffer undercount the
> > required pages because every ring buffer page contains a header
> > (BUF_PAGE_HDR_SIZE). Account for that header to ensure allocated remote
> > ring buffers aren't smaller than requested by the user.
> > 
> > While at it, ensure those functions catch nr_pages overflow.
> 
> Fixes patches should never have "while at it". That means it belongs as a
> separate patch. The only "while at it" that is acceptable is white space
> fixes or other formatting changes along with new code that is not a fix.

ack.

> 
> > 
> > Fixes: 2e67fabd8b77 ("ring-buffer: Introduce ring-buffer remotes")
> > Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
> > 
> > diff --git a/include/linux/ring_buffer.h b/include/linux/ring_buffer.h
> > index afc7daa6ee7d..7a1a92f87650 100644
> > --- a/include/linux/ring_buffer.h
> > +++ b/include/linux/ring_buffer.h
> > @@ -8,6 +8,8 @@
> >  
> >  #include <uapi/linux/trace_mmap.h>
> >  
> > +#include <linux/ring_buffer_types.h>
> 
> Hmm, why is this after the uapi header? It should be part of the linux/
> headers.
> 
> > +
> >  struct trace_buffer;
> >  struct ring_buffer_iter;
> >  
> > @@ -281,9 +283,14 @@ static inline struct ring_buffer_desc *__first_ring_buffer_desc(struct trace_buf
> >  
> >  static inline size_t trace_buffer_desc_size(size_t buffer_size, unsigned int nr_cpus)
> >  {
> > -	unsigned int nr_pages = max(DIV_ROUND_UP(buffer_size, PAGE_SIZE), 2UL) + 1;
> > +	unsigned long nr_pages =
> > +		max(DIV_ROUND_UP(buffer_size, PAGE_SIZE - BUF_PAGE_HDR_SIZE), 2UL) + 1;
> 
> This is getting a little unwieldy. Let's break it up:
> 
> 	unsigned long pages_req = DIV_ROUND_UP(buffer_size, PAGE_SIZE - BUF_PAGE_HDR_SIZE);
> 	unsigned long nr_pages = max(pages_req, 2UL) + 1;
> 
> Or better yet, let's add a new helper function:
> 
> static inline unsigned long calculate_nr_pages(size_t buffer_size)
> {
> 	unsigned long req_pages = DIV_ROUND_UP(buffer_size, PAGE_SIZE - BUF_PAGE_HDR_SIZE);
> 	return max(pages_req, 2UL) + 1;
> }

I'll introduce the helper from this patch as suggested.

> 
> Then this could be simply:
> 
> 	unsigned long nr_pages = calculate_nr_pages(buffer_size);
> 
> >  	struct ring_buffer_desc *rbdesc;
> >  
> > +	/* Capped by ring_buffer_desc::nr_page_va */
> > +	if (nr_pages > UINT_MAX)
> > +		return SIZE_MAX;
> 
> Separate patch.
> 
> > +
> >  	return size_add(offsetof(struct trace_buffer_desc, __data),
> >  			size_mul(nr_cpus, struct_size(rbdesc, page_va, nr_pages)));
> >  }
> > diff --git a/kernel/trace/trace_remote.c b/kernel/trace/trace_remote.c
> > index 75fa1ffc4c96..2e0fdbb730b7 100644
> > --- a/kernel/trace/trace_remote.c
> > +++ b/kernel/trace/trace_remote.c
> > @@ -980,9 +980,12 @@ int trace_remote_alloc_buffer(struct trace_buffer_desc *desc, size_t desc_size,
> >  			      const struct cpumask *cpumask)
> >  {
> >  	size_t min_desc_size = trace_buffer_desc_size(buffer_size, cpumask_weight(cpumask));
> > -	unsigned int nr_pages = max(DIV_ROUND_UP(buffer_size, PAGE_SIZE), 2UL) + 1;
> >  	struct ring_buffer_desc *rb_desc;
> >  	int cpu, ret = -ENOMEM;
> > +	unsigned int nr_pages;
> > +
> 
> 
> > +	if (min_desc_size == SIZE_MAX)
> > +		return -E2BIG;
> 
> Looks like this should be a separate patch too.
> 
> >  
> >  	if (desc_size < min_desc_size)
> >  		return -EINVAL;
> > @@ -991,6 +994,7 @@ int trace_remote_alloc_buffer(struct trace_buffer_desc *desc, size_t desc_size,
> >  	desc->struct_len = min_desc_size;
> >  
> >  	rb_desc = __first_ring_buffer_desc(desc);
> > +	nr_pages = max(DIV_ROUND_UP(buffer_size, PAGE_SIZE - BUF_PAGE_HDR_SIZE), 2UL) + 1;
> 
> And here we can have;
> 
> 	nr_pages = calculate_nr_pages(buffer_size);
> 
> -- Steve
> 
> >  
> >  	for_each_cpu(cpu, cpumask) {
> >  		unsigned int id;
> 

-- 
Vincent

  reply	other threads:[~2026-09-11 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 19:26 [PATCH v1 0/2] ring-buffer: Fix and unify size and page calculations Vincent Donnefort
2026-09-07 19:26 ` [PATCH v1 1/2] tracing/remotes: Account for ring buffer page header in size calculation Vincent Donnefort
2026-09-07 19:42   ` sashiko-bot
2026-09-09 22:13   ` Steven Rostedt
2026-09-11 14:32     ` Vincent Donnefort [this message]
2026-09-07 19:26 ` [PATCH v1 2/2] ring-buffer: Unify ring buffer minimum page calculations Vincent Donnefort
2026-09-07 19:42   ` sashiko-bot
2026-09-09 22:19   ` 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=aqQRGv26MEjjl1Br@google.com \
    --to=vdonnefort@google.com \
    --cc=kernel-team@android.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 \
    /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