mm/page_vma_mapped: continue past nonmatching huge PMDs
Subsystems (3)
PATCH 1/1 mm/page_vma_mapped: continue past nonmatching huge PMDs
A PTE-mapped large folio can straddle PMD boundaries after an unaligned mremap(). If the first part is discarded and replaced with an unrelated huge PMD, page_vma_mapped_walk() stops instead of looking for the rest of the folio in subsequent PMDs.
This also affects migration entries. A walk that stops at an unrelated huge PMD can leave migration PTEs behind when migration or an anonymous folio split restores the mappings. Those entries do not hold mapping references and can outlive the source folio.
Skip the current PMD rather than ending the walk on a flag or PFN mismatch. Do the same if the PMD became nonpresent before the locked recheck. Release the PMD lock, clear the per-PMD state and advance with step_forward(), so the existing range limit controls termination. This covers present, migration and device-private huge PMDs while preserving the matching-PMD and split-to-PTE paths.
--- mm/page_vma_mapped.c | 28 +++++++++++++++++++--------- 1 file changed, 19 insertions(+), 9 deletions(-)
mm/page_vma_mapped.c +19 -9
@@ -258,28 +258,28 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw)softleaf_t entry;if (!(pvmw->flags &PVMW_MIGRATION )) -return not_found (pvmw); + goto next_pmd; entry =softleaf_from_pmd (pmde);if (!check_pmd (softleaf_to_pfn (entry), pvmw)) -return not_found (pvmw); + goto next_pmd;return true; }else if (pmd_is_device_private_entry (pmde)) {softleaf_t entry;if (pvmw->flags &PVMW_MIGRATION ) -return not_found (pvmw); + goto next_pmd; entry =softleaf_from_pmd (pmde);if (!check_pmd (softleaf_to_pfn (entry), pvmw)) -return not_found (pvmw); + goto next_pmd;return true; }else if (!pmd_present (pmde)) { -return not_found (pvmw); + goto next_pmd; }if (likely (pmd_trans_huge (pmde))) {if (pvmw->flags &PVMW_MIGRATION ) -return not_found (pvmw); + goto next_pmd;if (!check_pmd (pmd_pfn (pmde), pvmw)) -return not_found (pvmw); + goto next_pmd;return true; }/* THP/device-private pmd was split under us: handle on pte level */
@@ -292,8 +292,7 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw) (pvmw->nr_pages >= HPAGE_PMD_NR))sync_with_folio_pmd_zap (mm, pvmw->pmd); -step_forward (pvmw,PMD_SIZE ); -continue ; + goto next_pmd; }if (!map_pte (pvmw, &pmde, &ptl)) {if (!pvmw->pte)
@@ -336,6 +335,17 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw) pvmw->ptl = ptl; } goto this_pte; +next_pmd: +/* +* A large folio can be PTE-mapped across PMDs, so a +* nonmatching PMD does not end the walk. +*/ +if (pvmw->ptl) { +spin_unlock (pvmw->ptl); + pvmw->ptl =NULL ; + } + pvmw->pmd =NULL ; +step_forward (pvmw,PMD_SIZE ); }while (pvmw->address < end);return false;
Signature · 1 line
2.55.0.openai.911.g06873a30d2f3
Andrew Morton
maintainerQuoted 10 lines · On Thu, 15 Oct 2026 18:15:49 -0700 Kyle Zeng <[email protected]> wrote:
A PTE-mapped large folio can straddle PMD boundaries after an unaligned
mremap(). If the first part is discarded and replaced with an unrelated huge PMD,page_vma_mapped_walk()stops instead of looking for the rest of the folio in subsequent PMDs.This also affects migration entries. A walk that stops at an unrelated huge PMD can leave migration PTEs behind when migration or an anonymous folio split restores the mappings. Those entries do not hold mapping references and can outlive the source folio.
Quoted 6 lines
Skip the current PMD rather than ending the walk on a flag or PFN mismatch. Do the same if the PMD became nonpresent before the locked recheck. Release the PMD lock, clear the per-PMD state and advance with
step_forward(), so the existing range limit controls termination. This covers present, migration and device-private huge PMDs while preserving the matching-PMD and split-to-PTE paths.
As always, when fixing a bug please describe the worst-case userspace-visible effects of the bug.
I asked $LLM and was told
: The worst credible effects are permanent application hangs, kernel : crashes, and potentially system-wide denial of service. Stale : migration entries can refer to freed and reused physical pages, causing : page faults to access unrelated folio metadata. Memory corruption is : possible but unproven; cross-process information disclosure has not : been established.
But you have an LLM too! So please never again send a bugfix without this info.
Also please explain whether there's a reproducer and if so, at least describe it and confirm the before-and-after results.
Thanks.
Quoted 31 lines · Andrew Morton
Quoted 10 lines · On Thu, 15 Oct 2026 18:15:49 -0700 Kyle Zeng <[email protected]> wrote:
A PTE-mapped large folio can straddle PMD boundaries after an unaligned
mremap(). If the first part is discarded and replaced with an unrelated huge PMD,page_vma_mapped_walk()stops instead of looking for the rest of the folio in subsequent PMDs.This also affects migration entries. A walk that stops at an unrelated huge PMD can leave migration PTEs behind when migration or an anonymous folio split restores the mappings. Those entries do not hold mapping references and can outlive the source folio.
Quoted 6 lines
Skip the current PMD rather than ending the walk on a flag or PFN mismatch. Do the same if the PMD became nonpresent before the locked recheck. Release the PMD lock, clear the per-PMD state and advance with
step_forward(), so the existing range limit controls termination. This covers present, migration and device-private huge PMDs while preserving the matching-PMD and split-to-PTE paths.As always, when fixing a bug please describe the worst-case userspace-visible effects of the bug.
I asked $LLM and was told
: The worst credible effects are permanent application hangs, kernel : crashes, and potentially system-wide denial of service. Stale : migration entries can refer to freed and reused physical pages, causing : page faults to access unrelated folio metadata. Memory corruption is : possible but unproven; cross-process information disclosure has not : been established.
Quoted 8 lines
But you have an LLM too! So please never again send a bugfix without this info.
Also please explain whether there's a reproducer and if so, at least describe it and confirm the before-and-after results.
Thanks.
Hi Andrew,
This issue can lead to memory corruption and I have a reproducer for it. I can update the description and send in a v2 if you think it is proper.
Best,
Kyle
Rik van Riel
reviewerQuoted 11 lines · Andrew Morton
As always, when fixing a bug please describe the worst-case userspace-visible effects of the bug.
But you have an LLM too! So please never again send a bugfix without this info.
Also please explain whether there's a reproducer and if so, at least describe it and confirm the before-and-after results.
I've been working on automating that for the past
few months.
The changelogs, comments, and code have needed fewer and fewer edits as the rules got adjusted over time.
https://github.com/rikvanriel/kernel-style
Signature · 1 line
All Rights Reversed.
Quoted 9 lines · Kyle Zeng
A PTE-mapped large folio can straddle PMD boundaries after an unaligned
mremap(). If the first part is discarded and replaced with an unrelated huge PMD,page_vma_mapped_walk()stops instead of looking for the rest of the folio in subsequent PMDs.This also affects migration entries. A walk that stops at an unrelated huge PMD can leave migration PTEs behind when migration or an anonymous folio split restores the mappings. Those entries do not hold mapping references and can outlive the source folio.
Quoted 8 lines
Quoted 1 line
Skip the current PMD rather than ending the walk on a flag or PFN
mismatch. Do the same if the PMD became nonpresent before the locked recheck. Release the PMD lock, clear the per-PMD state and advance with
step_forward(), so the existing range limit controls termination. This covers present, migration and device-private huge PMDs while preserving the matching-PMD and split-to-PTE paths.Fixes ace71a19cec5 ("mm: introduce page_vma_mapped_walk()")
THP migration was added in
616b8371539 ("mm: thp: enable thp migration in generic path")
which was a couple (3?) of release after ace71a19cec5. Doesn't really make a difference for backporting, so we can just keep the Fixes as is (it's the obvious right thing to do :) ).
Quoted 2 lines
Cc <[email protected]>Assisted-by LLM
We can drop these now.
Quoted 2 lines
Signed-off-by Kyle Zeng <[email protected]>---
Thanks!
Signature · 3 lines
Cheers, David