From: Sasha Levin <sashal@kernel.org>
To: Vincent Donnefort <vdonnefort@google.com>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
rostedt@goodmis.org, mhiramat@kernel.org,
linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, kernel-team@android.com,
linux-kernel@vger.kernel.org, Lee Jones <lee@kernel.org>
Subject: Re: STABLE REQ: [PATCH v5 06/10] tracing: Fix subbuf resize races with trace_pipe_raw readers
Date: Wed, 2 Sep 2026 18:14:05 -0400 [thread overview]
Message-ID: <20260902-daily-reply-0006-tracing-subbuf-resize-7-2@kernel.org> (raw)
In-Reply-To: <20260901123444.GA1350131@google.com>
> Concurrent subbuffer resizes may crash trace_pipe_raw readers or leak
> uninitialized memory to userspace due to stale size values.
>
> Fixes: bce761d75745 ("ring-buffer: Read and write to ring buffers with custom sub buffer size")
> Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
>
> Not sure if this is the latest version or not?
>
> I see review comments, but no v6. Anyway, no matter, it'll do.
Queued for 7.2, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-02 22:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260813131152.3589632-1-vdonnefort@google.com>
[not found] ` <20260813131152.3589632-7-vdonnefort@google.com>
2026-09-01 12:34 ` STABLE REQ: [PATCH v5 06/10] tracing: Fix subbuf resize races with trace_pipe_raw readers Lee Jones
2026-09-01 13:46 ` Steven Rostedt
2026-09-02 8:27 ` Lee Jones
2026-09-02 8:44 ` Greg KH
2026-09-02 9:57 ` Lee Jones
2026-09-02 11:38 ` Greg KH
2026-09-02 11:59 ` Lee Jones
2026-09-02 12:21 ` Steven Rostedt
2026-09-02 12:25 ` Steven Rostedt
2026-09-02 16:22 ` Lee Jones
2026-09-02 16:33 ` Steven Rostedt
2026-09-03 8:38 ` Lee Jones
2026-09-01 13:50 ` Vincent Donnefort
2026-09-02 22:14 ` Sasha Levin [this message]
2026-09-03 9:35 ` Vincent Donnefort
2026-09-03 12:34 ` Lee Jones
2026-09-03 12:44 ` STABLE REQ: [PATCH v5 06/10] tracing: Fix subbuf resize races with trace_pipe_raw readers\ Sasha Levin
2026-09-03 16:13 ` Lee Jones
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=20260902-daily-reply-0006-tracing-subbuf-resize-7-2@kernel.org \
--to=sashal@kernel.org \
--cc=kernel-team@android.com \
--cc=lee@kernel.org \
--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 \
--cc=vdonnefort@google.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