From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kiryl Shutsemau <kas@kernel.org>, Lance Yang <lance.yang@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ziy@nvidia.com, baolin.wang@linux.alibaba.com,
liam@infradead.org, nico.pache@linux.dev, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, usama.arif@linux.dev,
ljs@kernel.org, surenb@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] mm/huge_memory: fix pgtable withdrawal for huge zero PMDs
Date: Tue, 15 Sep 2026 17:03:19 +0200 [thread overview]
Message-ID: <1bbac1b4-b03a-4626-b509-c9f3ae36a169@kernel.org> (raw)
In-Reply-To: <aqlMvfIhr8nD9RHB@thinkstation>
On 9/15/26 15:52, Kiryl Shutsemau wrote:
> On Tue, Sep 15, 2026 at 09:43:15PM +0800, Lance Yang wrote:
>>
>>
>> On 2026/9/15 02:19, Andrew Morton wrote:
>>>
>>>
>>> Thanks. I'll remove cc:stable, move this into mm-unstable as a
>>> next-merge-window thing.
>>
>> Sounds good to me, thanks, Andrew!
>>
>> Kiryl, David, would you prefer the validation for raw-PFN mappings
>> of the huge zero page as a separate follow-up, or should that
>> validation replace this patch? wdyt
>
> I think this patch can be useful for graceful recovery if we somehow ended up
> with a zero page in a mapping where we shouldn't have one.
>
> A separate patch with validation would be great.
>
Ack
--
Cheers,
David
next prev parent reply other threads:[~2026-09-15 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 5:19 [PATCH 1/1] mm/huge_memory: fix pgtable withdrawal for huge zero PMDs Lance Yang
2026-09-13 6:46 ` Andrew Morton
2026-09-13 7:23 ` Lance Yang
2026-09-14 10:59 ` Kiryl Shutsemau
2026-09-14 14:29 ` David Hildenbrand (Arm)
2026-09-14 18:19 ` Andrew Morton
2026-09-15 13:43 ` Lance Yang
2026-09-15 13:52 ` Kiryl Shutsemau
2026-09-15 15:03 ` David Hildenbrand (Arm) [this message]
2026-09-15 15:13 ` David Hildenbrand (Arm)
2026-09-16 4:41 ` Lance Yang
2026-09-16 6:11 ` David Hildenbrand (Arm)
2026-09-16 6:44 ` Lance Yang
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=1bbac1b4-b03a-4626-b509-c9f3ae36a169@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=ziy@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.