From: Vincent Donnefort <vdonnefort@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] ring-buffer: Fixes for subbuf resizing
Date: Fri, 14 Aug 2026 09:25:51 +0100 [thread overview]
Message-ID: <an7RD18nj4ytlIfj@google.com> (raw)
In-Reply-To: <20260813215230.7aa47950@gandalf.local.home>
On Thu, Aug 13, 2026 at 09:52:30PM -0400, Steven Rostedt wrote:
> From: Vincent Donnefort <vdonnefort@google.com>
>
> This series addresses multiple issues discovered with the dynamic ring
> buffer resizing.
>
> Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> ---
>
> This is patches 1-5,7-9 of series: https://lore.kernel.org/all/20260813131152.3589632-1-vdonnefort@google.com/
>
> I'm running them through my tests right now. But I wanted to see what
> Sashiko thinks of them as one big patch. In the series, Sashiko kept
> complaining about existing issues that were fixed later in the series.
> Sending this as one big patch will hopefully have it give better feedback.
And it actually does not look bad!
The only comment left was fixed in "ring-buffer: Make nr_pages unsigned int",
which from Steven's feedback must be renamed as we may want to keep nr_pages
unsigned long where possible.
>
> kernel/trace/ring_buffer.c | 268 ++++++++++++++++++++++---------------
> 1 file changed, 158 insertions(+), 110 deletions(-)
>
[...]
prev parent reply other threads:[~2026-08-14 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 1:52 [PATCH] ring-buffer: Fixes for subbuf resizing Steven Rostedt
2026-08-14 2:09 ` sashiko-bot
2026-08-14 8:25 ` 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=an7RD18nj4ytlIfj@google.com \
--to=vdonnefort@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--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 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.