[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20251022194541.68c26d16b615ded15c5d3014@linux-foundation.org>
Date: Wed, 22 Oct 2025 19:45:41 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: Mike Rapoport <rppt@...nel.org>, brauner@...nel.org, corbet@....net,
graf@...zon.com, jgg@...pe.ca, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-mm@...ck.org, masahiroy@...nel.org,
ojeda@...nel.org, pratyush@...nel.org, rdunlap@...radead.org,
tj@...nel.org, jasonmiu@...gle.com, dmatlack@...gle.com,
skhawaja@...gle.com
Subject: Re: [PATCH v3 0/3] KHO: kfence + KHO memory corruption fix
On Tue, 21 Oct 2025 20:15:04 -0400 Pasha Tatashin <pasha.tatashin@...een.com> wrote:
> On Tue, Oct 21, 2025 at 4:53 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > On Tue, 21 Oct 2025 12:04:47 -0400 Pasha Tatashin <pasha.tatashin@...een.com> wrote:
> >
> > > > With liveupdate: dropped from the subjects
> > >
> > > I noticed "liveupdate: " subject prefix left over only after sending
> > > these patches. Andrew, would you like me to resend them, or could you
> > > remove the prefix from these patches?
> >
> > No problem.
> >
> > What should we do about -stable kernels?
> >
> > It doesn't seem worthwhile to backport a 3-patch series for a pretty
> > obscure bug. Perhaps we could merge a patch which disables this
>
> We are using KHO and have had obscure crashes due to this memory
> corruption, with stacks all over the place. I would prefer this fix to
> be properly backported to stable so we can also automatically consume
> it once we switch to the upstream KHO.
Oh.
I added this important info to the [0/N] changelog, added
Fixes: fc33e4b44b27 ("kexec: enable KHO support for memory preservation")
Cc: <stable@...r.kernel.org>
to all three and moved this into mm.git's mm-hotfixes branch.
Powered by blists - more mailing lists