From: Muchun Song <muchun.song@linux.dev>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: david@redhat.com, hughd@google.com, willy@infradead.org,
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,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 10/13] mm: page_vma_mapped_walk: map_pte() use pte_offset_map_rw_nolock()
Date: Tue, 24 Sep 2024 16:39:13 +0800 [thread overview]
Message-ID: <2CBAEE27-9C4E-4902-B6BB-B6029FD42E8D@linux.dev> (raw)
In-Reply-To: <cccc53fc-29c2-43c0-83d4-d330bade70c7@bytedance.com>
> On Sep 24, 2024, at 16:33, Qi Zheng <zhengqi.arch@bytedance.com> wrote:
>
>
>
> On 2024/9/24 16:25, Muchun Song wrote:
>>> On Sep 24, 2024, at 14:11, Qi Zheng <zhengqi.arch@bytedance.com> wrote:
>>>
>>> In the caller of map_pte(), we may modify the pvmw->pte after acquiring
>>> the pvmw->ptl, so convert it to using pte_offset_map_rw_nolock(). At
>>> this time, the pte_same() check is not performed after the pvmw->ptl held,
>>> so we should get pmdval and do pmd_same() check to ensure the stability of
>>> pvmw->pmd.
>>>
>>> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
>>> ---
>>> mm/page_vma_mapped.c | 25 ++++++++++++++++++++-----
>>> 1 file changed, 20 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/mm/page_vma_mapped.c b/mm/page_vma_mapped.c
>>> index ae5cc42aa2087..6410f29b37c1b 100644
>>> --- a/mm/page_vma_mapped.c
>>> +++ b/mm/page_vma_mapped.c
>>> @@ -13,9 +13,11 @@ static inline bool not_found(struct page_vma_mapped_walk *pvmw)
>>> return false;
>>> }
>>>
>>> -static bool map_pte(struct page_vma_mapped_walk *pvmw, spinlock_t **ptlp)
>>> +static bool map_pte(struct page_vma_mapped_walk *pvmw, pmd_t *pmdvalp,
>>> + spinlock_t **ptlp)
>>> {
>>> pte_t ptent;
>>> + pmd_t pmdval;
>> Why declare a new variable? Can’t we use *pmdvalp instead?
>
> It's just a coding habit, both are fine for me.
Agree. But sometime it could make code look a little simpler.
>
>>>
>>> if (pvmw->flags & PVMW_SYNC) {
>>> /* Use the stricter lookup */
>>> @@ -25,6 +27,7 @@ static bool map_pte(struct page_vma_mapped_walk *pvmw, spinlock_t **ptlp)
>>> return !!pvmw->pte;
>>> }
>>>
>>> +again:
>>> /*
>>> * It is important to return the ptl corresponding to pte,
>>> * in case *pvmw->pmd changes underneath us; so we need to
>>> @@ -32,10 +35,11 @@ static bool map_pte(struct page_vma_mapped_walk *pvmw, spinlock_t **ptlp)
>>> * proceeds to loop over next ptes, and finds a match later.
>>> * Though, in most cases, page lock already protects this.
>>> */
>>> - pvmw->pte = pte_offset_map_nolock(pvmw->vma->vm_mm, pvmw->pmd,
>>> - pvmw->address, ptlp);
>>> + pvmw->pte = pte_offset_map_rw_nolock(pvmw->vma->vm_mm, pvmw->pmd,
>>> + pvmw->address, &pmdval, ptlp);
>>> if (!pvmw->pte)
>>> return false;
>>> + *pmdvalp = pmdval;
For instance, here, it is unnecessary if pmdvalp is passed directly to
pte_offset_map_rw_nolock.
>>>
>>> ptent = ptep_get(pvmw->pte);
>>>
>>> @@ -67,8 +71,13 @@ static bool map_pte(struct page_vma_mapped_walk *pvmw, spinlock_t **ptlp)
>>> } else if (!pte_present(ptent)) {
>>> return false;
>>> }
>>> + spin_lock(*ptlp);
>>> + if (unlikely(!pmd_same(pmdval, pmdp_get_lockless(pvmw->pmd)))) {
>>> + pte_unmap_unlock(pvmw->pte, *ptlp);
>>> + goto again;
>>> + }
>>> pvmw->ptl = *ptlp;
>>> - spin_lock(pvmw->ptl);
>>> +
>>> return true;
>>> }
>>>
>>> @@ -278,7 +287,7 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw)
>>> step_forward(pvmw, PMD_SIZE);
>>> continue;
>>> }
>>> - if (!map_pte(pvmw, &ptl)) {
>>> + if (!map_pte(pvmw, &pmde, &ptl)) {
>>> if (!pvmw->pte)
>>> goto restart;
>>> goto next_pte;
>>> @@ -307,6 +316,12 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw)
>>> if (!pvmw->ptl) {
>>> pvmw->ptl = ptl;
>>> spin_lock(pvmw->ptl);
>>> + if (unlikely(!pmd_same(pmde, pmdp_get_lockless(pvmw->pmd)))) {
>>> + pte_unmap_unlock(pvmw->pte, pvmw->ptl);
>>> + pvmw->ptl = NULL;
>>> + pvmw->pte = NULL;
>>> + goto restart;
>>> + }
>>> }
>>> goto this_pte;
>>> } while (pvmw->address < end);
>>> --
>>> 2.20.1
next prev parent reply other threads:[~2024-09-24 8:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 6:09 [PATCH v4 00/13] introduce pte_offset_map_{ro|rw}_nolock() Qi Zheng
2024-09-24 6:09 ` [PATCH v4 01/13] mm: pgtable: " Qi Zheng
2024-09-24 6:24 ` Muchun Song
2024-09-24 12:58 ` David Hildenbrand
2024-09-24 6:09 ` [PATCH v4 02/13] powerpc: assert_pte_locked() use pte_offset_map_ro_nolock() Qi Zheng
2024-09-24 6:09 ` [PATCH v4 03/13] mm: filemap: filemap_fault_recheck_pte_none() " Qi Zheng
2024-09-24 6:09 ` [PATCH v4 04/13] mm: khugepaged: __collapse_huge_page_swapin() " Qi Zheng
2024-09-24 6:09 ` [PATCH v4 05/13] arm: adjust_pte() use pte_offset_map_rw_nolock() Qi Zheng
2024-09-24 6:09 ` [PATCH v4 06/13] mm: handle_pte_fault() " Qi Zheng
2024-09-24 6:09 ` [PATCH v4 07/13] mm: khugepaged: collapse_pte_mapped_thp() " Qi Zheng
2024-09-24 7:14 ` Muchun Song
2024-09-24 7:29 ` Qi Zheng
2024-09-24 8:52 ` Muchun Song
2024-09-24 8:57 ` Qi Zheng
2024-09-24 9:03 ` Muchun Song
2024-09-24 6:10 ` [PATCH v4 08/13] mm: copy_pte_range() " Qi Zheng
2024-09-24 7:35 ` Muchun Song
2024-09-24 6:10 ` [PATCH v4 09/13] mm: mremap: move_ptes() " Qi Zheng
2024-09-24 7:39 ` Muchun Song
2024-09-24 6:10 ` [PATCH v4 10/13] mm: page_vma_mapped_walk: map_pte() " Qi Zheng
2024-09-24 8:25 ` Muchun Song
2024-09-24 8:33 ` Qi Zheng
2024-09-24 8:39 ` Muchun Song [this message]
2024-09-24 8:45 ` Qi Zheng
2024-09-24 6:10 ` [PATCH v4 11/13] mm: userfaultfd: move_pages_pte() " Qi Zheng
2024-09-24 6:10 ` [PATCH v4 12/13] mm: multi-gen LRU: walk_pte_range() " Qi Zheng
2024-09-24 14:39 ` David Hildenbrand
2024-09-24 6:10 ` [PATCH v4 13/13] mm: pgtable: remove pte_offset_map_nolock() Qi Zheng
2024-09-24 13:02 ` David Hildenbrand
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=2CBAEE27-9C4E-4902-B6BB-B6029FD42E8D@linux.dev \
--to=muchun.song@linux.dev \
--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=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 \
--cc=zhengqi.arch@bytedance.com \
/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