[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251103172321.689294e48c2fae795e114ce6@linux-foundation.org>
Date: Mon, 3 Nov 2025 17:23:21 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pratyush Yadav <pratyush@...nel.org>, Baoquan He <bhe@...hat.com>,
Alexander Graf <graf@...zon.com>, Mike Rapoport <rppt@...nel.org>, Pasha
Tatashin <pasha.tatashin@...een.com>, kexec@...ts.infradead.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] kho: misc fixes
On Mon, 3 Nov 2025 16:20:20 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Mon, 3 Nov 2025 19:02:30 +0100 Pratyush Yadav <pratyush@...nel.org> wrote:
>
> > This series has a couple of misc fixes for KHO I discovered during code
> > review and testing.
> >
> > The series is based on top of [0] which has another fix for the function
> > touched by patch 1. I spotted these two after sending the patch. If that
> > one needs a reroll, I can combine the three into a series.
> >
>
> Things appear to be misordered here.
>
> [1/2] "kho: fix unpreservation of higher-order vmalloc preservations"
> fixes a667300bd53f2, so it's wanted in 6.18-rcX
>
> [2/2] "kho: warn and exit when unpreserved page wasn't preserved"
> fixes fc33e4b44b271, so it's wanted in 6.16+
>
> So can we please have [2/2] as a standalone fix against latest -linus,
> with a cc:stable?
>
> And then [1/2] as a standalone fix against latest -linus without a
> cc:stable.
>
OK, I think I figured it out.
In mm-hotfixes-unstable I have
kho-fix-out-of-bounds-access-of-vmalloc-chunk.patch
kho-fix-unpreservation-of-higher-order-vmalloc-preservations.patch
kho-warn-and-exit-when-unpreserved-page-wasnt-preserved.patch
The first two are applicable to 6.18-rcX and the third is applicable to
6.18-rcX, with a cc:stable for backporting.
Powered by blists - more mailing lists