From: Harry Yoo <harry.yoo@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Suren Baghdasaryan <surenb@google.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
David Hildenbrand <david@redhat.com>, Kees Cook <kees@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Shakeel Butt <shakeel.butt@linux.dev>,
Mike Rapoport <rppt@kernel.org>, Michal Hocko <mhocko@suse.com>,
Jonathan Corbet <corbet@lwn.net>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>, Rik van Riel <riel@surriel.com>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Harry Yoo <harry.yoo@oracle.com>
Subject: [PATCH V1 2/2] mm: document when rmap locks can be skipped when setting need_rmap_locks
Date: Tue, 26 Aug 2025 15:58:48 +0900 [thread overview]
Message-ID: <20250826065848.346066-2-harry.yoo@oracle.com> (raw)
In-Reply-To: <20250826065848.346066-1-harry.yoo@oracle.com>
While move_ptes() explains when rmap locks can be skipped, when reading
the code setting pmc.need_rmap_locks it is not immediately obvious when
need_rmap_locks can be false. Add a brief explanation in copy_vma() and
relocate_vma_down(), and add a pointer to the comment in move_ptes().
Meanwhile, fix and improve the comment in move_ptes().
Signed-off-by: Harry Yoo <harry.yoo@oracle.com>
---
mm/mremap.c | 4 +++-
mm/vma.c | 7 +++++++
mm/vma_exec.c | 5 +++++
3 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/mm/mremap.c b/mm/mremap.c
index e618a706aff5..86adb872bea0 100644
--- a/mm/mremap.c
+++ b/mm/mremap.c
@@ -218,8 +218,10 @@ static int move_ptes(struct pagetable_move_control *pmc,
* When need_rmap_locks is false, we use other ways to avoid
* such races:
*
- * - During exec() shift_arg_pages(), we use a specially tagged vma
+ * - During exec() relocate_vma_down(), we use a specially tagged vma
* which rmap call sites look for using vma_is_temporary_stack().
+ * Folios mapped in the temporary stack vma cannot be migrated until
+ * the relocation is complete.
*
* - During mremap(), new_vma is often known to be placed after vma
* in rmap traversal order. This ensures rmap will always observe
diff --git a/mm/vma.c b/mm/vma.c
index 3b12c7579831..3da49f79e9ba 100644
--- a/mm/vma.c
+++ b/mm/vma.c
@@ -1842,6 +1842,11 @@ struct vm_area_struct *copy_vma(struct vm_area_struct **vmap,
vmg.next = vma_iter_next_rewind(&vmi, NULL);
new_vma = vma_merge_new_range(&vmg);
+ /*
+ * rmap locks can be skipped as long as new_vma is traversed
+ * after vma during rmap walk (new_vma->vm_pgoff >= vma->vm_pgoff).
+ * See the comment in move_ptes().
+ */
if (new_vma) {
/*
* Source vma may have been merged into new_vma
@@ -1879,6 +1884,8 @@ struct vm_area_struct *copy_vma(struct vm_area_struct **vmap,
new_vma->vm_ops->open(new_vma);
if (vma_link(mm, new_vma))
goto out_vma_link;
+
+ /* new_vma->pg_off is always >= vma->pg_off if not merged */
*need_rmap_locks = false;
}
return new_vma;
diff --git a/mm/vma_exec.c b/mm/vma_exec.c
index 922ee51747a6..a895dd39ac46 100644
--- a/mm/vma_exec.c
+++ b/mm/vma_exec.c
@@ -63,6 +63,11 @@ int relocate_vma_down(struct vm_area_struct *vma, unsigned long shift)
* process cleanup to remove whatever mess we made.
*/
pmc.for_stack = true;
+ /*
+ * pmc.need_rmap_locks is false since rmap locks can be safely skipped
+ * because migration is disabled for this vma during relocation.
+ * See the comment in move_ptes().
+ */
if (length != move_page_tables(&pmc))
return -ENOMEM;
--
2.43.0
next prev parent reply other threads:[~2025-08-26 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 6:58 [PATCH V1 1/2] docs/mm: explain when and why rmap locks need to be taken during mremap() Harry Yoo
2025-08-26 6:58 ` Harry Yoo [this message]
2025-08-26 9:46 ` [PATCH V1 2/2] mm: document when rmap locks can be skipped when setting need_rmap_locks Lorenzo Stoakes
2025-08-27 6:52 ` Harry Yoo
2025-08-27 11:16 ` Lorenzo Stoakes
2025-08-26 7:22 ` [PATCH V1 1/2] docs/mm: explain when and why rmap locks need to be taken during mremap() Jonathan Corbet
2025-08-26 8:37 ` Lorenzo Stoakes
2025-08-26 9:48 ` Harry Yoo
2025-08-26 9:58 ` Lorenzo Stoakes
2025-08-27 7:18 ` Harry Yoo
2025-08-27 9:25 ` Lorenzo Stoakes
2025-08-26 9:55 ` Lorenzo Stoakes
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=20250826065848.346066-2-harry.yoo@oracle.com \
--to=harry.yoo@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox