From: Qi Zheng <zhengqi.arch@bytedance.com>
To: david@redhat.com, hughd@google.com, willy@infradead.org,
muchun.song@linux.dev, vbabka@kernel.org,
akpm@linux-foundation.org, rppt@kernel.org,
vishal.moola@gmail.com, peterx@redhat.com, ryan.roberts@arm.com,
christophe.leroy2@cs-soprasteria.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org,
Qi Zheng <zhengqi.arch@bytedance.com>
Subject: [PATCH v2 11/14] mm: userfaultfd: move_pages_pte() use pte_offset_map_rw_nolock()
Date: Thu, 22 Aug 2024 15:13:26 +0800 [thread overview]
Message-ID: <d4e0c8970662ecc88352822e6d81a11b4dd72b1e.1724310149.git.zhengqi.arch@bytedance.com> (raw)
In-Reply-To: <cover.1724310149.git.zhengqi.arch@bytedance.com>
In move_pages_pte(), we may modify the dst_pte and src_pte after acquiring
the ptl, so convert it to using pte_offset_map_rw_nolock(). But since we
already do the pte_same() check, there is no need to get pmdval to do
pmd_same() check, just pass a dummy variable to it.
Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
---
mm/userfaultfd.c | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
index 6ef42d9cd482e..414ee744257b7 100644
--- a/mm/userfaultfd.c
+++ b/mm/userfaultfd.c
@@ -1135,7 +1135,7 @@ static int move_pages_pte(struct mm_struct *mm, pmd_t *dst_pmd, pmd_t *src_pmd,
spinlock_t *src_ptl, *dst_ptl;
pte_t *src_pte = NULL;
pte_t *dst_pte = NULL;
-
+ pmd_t dummy_pmdval;
struct folio *src_folio = NULL;
struct anon_vma *src_anon_vma = NULL;
struct mmu_notifier_range range;
@@ -1146,7 +1146,14 @@ static int move_pages_pte(struct mm_struct *mm, pmd_t *dst_pmd, pmd_t *src_pmd,
src_addr, src_addr + PAGE_SIZE);
mmu_notifier_invalidate_range_start(&range);
retry:
- dst_pte = pte_offset_map_nolock(mm, dst_pmd, dst_addr, &dst_ptl);
+ /*
+ * Use the maywrite version to indicate that dst_pte will be modified,
+ * but since we will use pte_same() to detect the change of the pte
+ * entry, there is no need to get pmdval, so just pass a dummy variable
+ * to it.
+ */
+ dst_pte = pte_offset_map_rw_nolock(mm, dst_pmd, dst_addr, &dummy_pmdval,
+ &dst_ptl);
/* Retry if a huge pmd materialized from under us */
if (unlikely(!dst_pte)) {
@@ -1154,7 +1161,9 @@ static int move_pages_pte(struct mm_struct *mm, pmd_t *dst_pmd, pmd_t *src_pmd,
goto out;
}
- src_pte = pte_offset_map_nolock(mm, src_pmd, src_addr, &src_ptl);
+ /* same as dst_pte */
+ src_pte = pte_offset_map_rw_nolock(mm, src_pmd, src_addr, &dummy_pmdval,
+ &src_ptl);
/*
* We held the mmap_lock for reading so MADV_DONTNEED
--
2.20.1
next prev parent reply other threads:[~2024-08-22 7:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 7:13 [PATCH v2 00/14] introduce pte_offset_map_{ro|rw}_nolock() Qi Zheng
2024-08-22 7:13 ` [PATCH v2 01/14] mm: pgtable: " Qi Zheng
2024-08-26 3:45 ` [PATCH v2 01/14 update] " Qi Zheng
2024-08-26 15:21 ` [PATCH v2 01/14] " David Hildenbrand
2024-08-27 4:33 ` Qi Zheng
2024-08-28 10:48 ` David Hildenbrand
2024-08-29 3:27 ` Qi Zheng
2024-08-29 10:59 ` Qi Zheng
2024-08-29 15:31 ` David Hildenbrand
2024-08-30 6:37 ` Qi Zheng
2024-08-28 9:48 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 02/14] arm: adjust_pte() use pte_offset_map_rw_nolock() Qi Zheng
2024-08-26 15:26 ` David Hildenbrand
2024-08-29 3:39 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 03/14] powerpc: assert_pte_locked() use pte_offset_map_ro_nolock() Qi Zheng
2024-08-26 15:28 ` David Hildenbrand
2024-08-29 7:21 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 04/14] mm: filemap: filemap_fault_recheck_pte_none() " Qi Zheng
2024-08-26 15:29 ` David Hildenbrand
2024-08-29 7:23 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 05/14] mm: khugepaged: __collapse_huge_page_swapin() " Qi Zheng
2024-08-26 15:33 ` David Hildenbrand
2024-08-29 7:25 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 06/14] mm: handle_pte_fault() use pte_offset_map_rw_nolock() Qi Zheng
2024-08-26 15:36 ` David Hildenbrand
2024-08-27 4:53 ` Qi Zheng
2024-08-29 7:30 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 07/14] mm: khugepaged: collapse_pte_mapped_thp() " Qi Zheng
2024-08-29 8:10 ` Muchun Song
2024-08-30 6:54 ` Qi Zheng
2024-09-05 6:32 ` Muchun Song
2024-09-05 6:41 ` Qi Zheng
2024-09-05 7:18 ` Muchun Song
2024-08-22 7:13 ` [PATCH v2 08/14] mm: copy_pte_range() " Qi Zheng
2024-08-29 8:13 ` Muchun Song
2024-08-29 15:36 ` David Hildenbrand
2024-08-30 6:42 ` Qi Zheng
2024-08-22 7:13 ` [PATCH v2 09/14] mm: mremap: move_ptes() " Qi Zheng
2024-08-22 7:13 ` [PATCH v2 10/14] mm: page_vma_mapped_walk: map_pte() " Qi Zheng
2024-08-22 7:13 ` Qi Zheng [this message]
2024-08-22 7:13 ` [PATCH v2 12/14] mm: multi-gen LRU: walk_pte_range() " Qi Zheng
2024-08-22 7:13 ` [PATCH v2 13/14] mm: pgtable: remove pte_offset_map_nolock() Qi Zheng
2024-08-22 7:13 ` [PATCH v2 14/14] mm: khugepaged: retract_page_tables() use pte_offset_map_rw_nolock() Qi Zheng
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=d4e0c8970662ecc88352822e6d81a11b4dd72b1e.1724310149.git.zhengqi.arch@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy2@cs-soprasteria.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=muchun.song@linux.dev \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=vbabka@kernel.org \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.org \
/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