On Thu, Sep 03, 2026 at 01:34:55PM +0100, Lee Jones wrote:
On Thu, 03 Sep 2026, Vincent Donnefort wrote:
On Wed, Sep 02, 2026 at 06:14:05PM -0400, Sasha Levin wrote:
> > 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 <[email protected]>
> >
> > 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
This isn't the last version of this patch, I have just posted a v9 [1] and
Steven hasn't reviewed it yet.
[1] https://lore.kernel.org/all/[email protected]/
The confusion is mine to own. I responded to the wrong patch mail, sorry!
`ring-buffer: Fix subbuf resize race with ring buffer readers`
Which is in Mainline with the immutable SHA 8a5f63637890. My assumption
is that Sasha queued the correct commit or the tools would have
complained loudly.
Indeed, sorry for the confusion! I've queued 8a5f63637890 ("ring-buffer: Fix
subbuf resize race with ring buffer readers") for 7.2.
--
Thanks,
Sasha
