mm-rmap-warn-on-new-pte-mapped-folios-in-page_add_anon_rmap.patch removed from -mm tree
The quilt patch titled
Subject: mm/rmap: warn on new PTE-mapped folios in page_add_anon_rmap()
has been removed from the -mm tree. Its filename was
mm-rmap-warn-on-new-pte-mapped-folios-in-page_add_anon_rmap.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: David Hildenbrand <[email protected]>
Subject: mm/rmap: warn on new PTE-mapped folios in page_add_anon_rmap()
Date: Wed, 13 Sep 2023 14:51:11 +0200
If swapin code would ever decide to not use order-0 pages and supply a PTE-mapped large folio, we will have to change how we call __folio_set_anon() -- eventually with exclusive=false and an adjusted address. For now, let's add a VM_WARN_ON_FOLIO() with a comment about the situation.
---
mm/rmap.c | 7 +++++++ 1 file changed, 7 insertions(+)
mm/rmap.c renamed from mm/rmap.c~mm-rmap-warn-on-new-pte-mapped-folios-in-page_add_anon_rmap +7 -0
@@ -1238,6 +1238,13 @@ void page_add_anon_rmap(struct page *pagif (unlikely (!folio_test_anon (folio))) {VM_WARN_ON_FOLIO (!folio_test_locked (folio), folio); +/* +* For a PTE-mapped large folio, we only know that the single +* PTE is exclusive. Further, __folio_set_anon() might not get +* folio->index right when not given the address of the head +* page. +*/ +VM_WARN_ON_FOLIO (folio_test_large (folio) && !compound, folio);__folio_set_anon (folio, vma, address, !!(flags &RMAP_EXCLUSIVE )); }else if (likely (!folio_test_ksm (folio))) {
_
Patches currently in -mm which might be from [email protected] are
mm-rmap-move-setpageanonexclusive-out-of-page_move_anon_rmap.patch mm-rmap-convert-page_move_anon_rmap-to-folio_move_anon_rmap.patch memory-move-exclusivity-detection-in-do_wp_page-into-wp_can_reuse_anon_folio.patch