Re: STABLE REQ: [PATCH v5 06/10] tracing: Fix subbuf resize races with trace_pipe_raw readers

[Lee Jones <lee@kernel.org>]

On Wed, 02 Sep 2026, Steven Rostedt wrote:

> On Wed, 2 Sep 2026 08:21:41 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > There's even been times that I *removed* a Cc to stable because I did not
> > think it was worth the backport. Of course, I still keep the Fixes tag,
> > which means it will likely be backported anyway. But that's up to the
> > stable maintainers to decide ;-)

Pretty sure this isn't the case anymore.  RIP AUTOSEL.

> The big difference between a commit with the Fixes tag and a Cc to stable
> verses one with the Fixes tag without the Cc stable, is that the one with
> Cc stable will give me a "FAILED" message if it fails to apply. One with
> just the Fixes tag and no Cc stable, will not generate that message to me
> if it doesn't apply back to the version with the Fixes commit sha.

So what happens when you receive the FAILED message?

And why are you interested to know how far back a fix can be backported?

Personally, I'm _very_ interested in a _small_ number of patches, but
none of which usually emanate from subsystems I maintain.

> I do like to know what I marked as stable and fails to apply. Unfortunately
> I don't have the time to go fix them. But I keep them in a mail folder in
> case I need to do it one day.

We have have such wonderful aspirations.  Maybe we can get around to
those jobs when AI starts doing our jobs for us!  =;-)

-- 
Lee Jones