From: Vincent Donnefort <vdonnefort@google.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH 0/1] ring-buffer: Fix sub-buffer order updates and free_page leaks
Date: Thu, 13 Aug 2026 18:25:32 +0100 [thread overview]
Message-ID: <an3-DCFFkOo4LSR5@google.com> (raw)
In-Reply-To: <178663776361.475864.7685868697103378735.stgit@devnote2>
On Fri, Aug 14, 2026 at 01:16:03AM +0900, Masami Hiramatsu (Google) wrote:
> Hi Vincent,
>
> Here is my patch to fix the race and free_page problem.
> Let's see what Sashiko says for this.
>
> Thank you,
>
> ---
> base-commit: 3d6d817622b0a9721e3cc404df3469171582be13
>
> Masami Hiramatsu (Google) (1):
> ring-buffer: Fix race between ring_buffer_subbuf_order_set() and readers
>
>
> kernel/trace/ring_buffer.c | 35 +++++++++++++++++++++++++++++------
> 1 file changed, 29 insertions(+), 6 deletions(-)
>
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>
Sorry I am not sure to understand what is wrong with that series I made here?
https://lore.kernel.org/all/20260813131152.3589632-1-vdonnefort@google.com/
--
Vincent
prev parent reply other threads:[~2026-08-13 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 16:16 [PATCH 0/1] ring-buffer: Fix sub-buffer order updates and free_page leaks Masami Hiramatsu (Google)
2026-08-13 16:16 ` [PATCH] ring-buffer: Fix race between ring_buffer_subbuf_order_set() and readers Masami Hiramatsu (Google)
2026-08-13 16:30 ` sashiko-bot
2026-08-13 17: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=an3-DCFFkOo4LSR5@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 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.