From: Andrew Morton <akpm@linux-foundation.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Baoquan He <bhe@redhat.com>, Alexander Graf <graf@amazon.com>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] kho: misc fixes
Date: Mon, 3 Nov 2025 16:20:20 -0800 [thread overview]
Message-ID: <20251103162020.ac696dbc695f9341e7a267f7@linux-foundation.org> (raw)
In-Reply-To: <20251103180235.71409-1-pratyush@kernel.org>
On Mon, 3 Nov 2025 19:02:30 +0100 Pratyush Yadav <pratyush@kernel.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.
Once I have those merged up we can then take a look at what to do about
the 6.19 material which is presently queued in mm-unstable.
Thanks.
next prev parent reply other threads:[~2025-11-04 0:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 18:02 Pratyush Yadav
2025-11-03 18:02 ` [PATCH 1/2] kho: fix unpreservation of higher-order vmalloc preservations Pratyush Yadav
2025-11-04 14:31 ` Mike Rapoport
2025-11-03 18:02 ` [PATCH 2/2] kho: warn and exit when unpreserved page wasn't preserved Pratyush Yadav
2025-11-04 14:32 ` Mike Rapoport
2025-11-04 0:20 ` Andrew Morton [this message]
2025-11-04 1:23 ` [PATCH 0/2] kho: misc fixes Andrew Morton
2025-11-05 10:06 ` Pratyush Yadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251103162020.ac696dbc695f9341e7a267f7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox