mm-khugepaged-flush-deferred-unmaps-before-dropping-a-failed-folio.patch removed from -mm tree
The quilt patch titled
Subject: mm/khugepaged: flush deferred unmaps before dropping a failed folio
has been removed from the -mm tree. Its filename was
mm-khugepaged-flush-deferred-unmaps-before-dropping-a-failed-folio.patch
This patch was dropped because it was merged into the mm-hotfixes-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Kyle Zeng <[email protected]>
Subject: mm/khugepaged: flush deferred unmaps before dropping a failed folio
Date: Tue, 6 Oct 2026 21:10:01 -0700
collapse_file() can fail its reference-count or dirty-folio check after unmapping with TTU_BATCH_FLUSH. Both paths put back the isolated folio, then unlock it and drop the lookup reference before reaching the common try_to_unmap_flush().
The page-cache reference does not keep the folio stable once the lock is released. Another collapse can replace and free it. With its PTEs already gone, that collapse cannot flush the first task's per-task TLB batch, and retract_page_tables() skips short or unaligned VMAs. A CPU can therefore retain a user translation to the freed folio. This has been reproduced with unprivileged MADV_COLLAPSE on a memfd.
Flush at out_unlock while the lookup reference and folio lock are still held. The common flush continues to cover the accumulated pagelist on both success and rollback, preserving batching on successful collapses.
---
mm/khugepaged.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
mm/khugepaged.c renamed from mm/khugepaged.c~mm-khugepaged-flush-deferred-unmaps-before-dropping-a-failed-folio +7 -3
@@ -2467,6 +2467,11 @@ static enum scan_result collapse_file(st index +=folio_nr_pages (folio);continue ; out_unlock: +/* +* The folio may have been unmapped with TTU_BATCH_FLUSH. +* Flush before releasing the lock and our last reference. +*/ +try_to_unmap_flush ();folio_unlock (folio);folio_put (folio); goto xa_unlocked;
@@ -2477,9 +2482,8 @@ xa_locked: xa_unlocked:/* -* If collapse is successful, flush must be done now before copying. -* If collapse is unsuccessful, does flush actually need to be done? -* Do it anyway, to clear the state. +* Flush before copying the folios, or releasing them in rollback. +* This is a no-op if out_unlock already flushed the batch. */ try_to_unmap_flush ();
_
Patches currently in -mm which might be from [email protected] are