Re: hunting memory corruption bug in 6.18.x

[Yosry Ahmed]

On Mon, Oct 19, 2026 at 11:15 AM Borislav Petkov <bp@xxxxxxxxx> wrote:
>
> On Mon, Oct 19, 2026 at 11:00:00AM -0700, Yosry Ahmed wrote:
> > Right, but this is for new patches that get merged into Linus's tree,
> > what about existing patches? Any way to retrigger that workflow?
>
> You take your patch, apply it to the stable trees here:
>
> https://www.kernel.org/category/releases.html
>
> and send the applied and tested version it to <stable@xxxxxxxxxx>.
>
> I.e., you backport it yourself. :)

Will do, I have done manual backports before but only for conflicts. I
was more asking if I need to send the patch to all branches or if it
will be automatically backported to the others if there are no
conflicts.

>
> Do git-log on those branches to see how stable backports are annotated. It
> needs to say:
>
> "Commit <sha1> upstream."
>
> at the top.
>
> There's also Documentation/process/stable-kernel-rules.rst
>
> HTH.
>
> --
> Regards/Gruss,
>     Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette