mm-rmap-drop-stale-comment-in-page_add_anon_rmap-and-hugepage_add_anon_rmap.patch removed from -mm tree
The quilt patch titled
Subject: mm/rmap: drop stale comment in page_add_anon_rmap and hugepage_add_anon_rmap()
has been removed from the -mm tree. Its filename was
mm-rmap-drop-stale-comment-in-page_add_anon_rmap-and-hugepage_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: drop stale comment in page_add_anon_rmap and hugepage_add_anon_rmap()
Date: Wed, 13 Sep 2023 14:51:08 +0200
Patch series "Anon rmap cleanups".
Some cleanups around rmap for anon pages. I'm working on more cleanups also around file rmap -- also to handle the "compound" parameter internally only and to let hugetlb use page_add_file_rmap(), but these changes make sense separately.
This patch (of 6):
That comment was added in commit 5dbe0af47f8a ("mm: fix kernel BUG at mm/rmap.c:1017!") to document why we can see vma->vm_end getting adjusted concurrently due to a VMA split.
However, the optimized locking code was changed again in bf181b9f9d8 ("mm anon rmap: replace same_anon_vma linked list with an interval tree.").
... and later, the comment was changed in commit 0503ea8f5ba7 ("mm/mmap:
remove __vma_adjust()") to talk about "vma_merge" although the original issue was with VMA splitting.
Let's just remove that comment. Nowadays, it's outdated, imprecise and confusing.
---
mm/rmap.c | 2 -- 1 file changed, 2 deletions(-)
mm/rmap.c renamed from mm/rmap.c~mm-rmap-drop-stale-comment-in-page_add_anon_rmap-and-hugepage_add_anon_rmap +0 -2
@@ -1245,7 +1245,6 @@ void page_add_anon_rmap(struct page *pag__lruvec_stat_mod_folio (folio,NR_ANON_MAPPED , nr);if (likely (!folio_test_ksm (folio))) { -/* address might be in next vma when migration races vma_merge */ if (first)__page_set_anon_rmap (folio, page, vma, address, !!(flags &RMAP_EXCLUSIVE ));
@@ -2549,7 +2548,6 @@ void hugepage_add_anon_rmap(struct pageBUG_ON (!folio_test_locked (folio));BUG_ON (!anon_vma); -/* address might be in next vma when migration races vma_merge */ first =atomic_inc_and_test (&folio->_entire_mapcount);VM_BUG_ON_PAGE (!first && (flags &RMAP_EXCLUSIVE ), page);VM_BUG_ON_PAGE (!first &&PageAnonExclusive (page), page);
_
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