From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_vma_mapped_walk: add missing pgtable entry accessors
Date: Mon, 4 May 2026 14:42:55 +0200 [thread overview]
Message-ID: <40ab8829-5f70-4474-9cf5-2c8da96d56d6@kernel.org> (raw)
In-Reply-To: <20260503065113.3385165A37-agordeev@linux.ibm.com>
On 5/3/26 08:51, Alexander Gordeev wrote:
> On Fri, May 01, 2026 at 09:01:09PM +0200, David Hildenbrand (Arm) wrote:
>> On 4/29/26 15:47, Alexander Gordeev wrote:
>>>
>>> (*)
>>>
>>>
>>> Ok, that is a different topic. I actually tried to resolve the lockless
>>> issue(s) in (*) while the direct dereferences just seemed to be relevant
>>> to go along (similarly to the GUP patch).
>>>
>>> But I would rather resend ptep_get() => ptep_get_lockless() fixes for
>>> this patch.
>>>
>>> Would it work?
>>
>> You mean only sending {*) ?
>
> Only this:
>
> diff --git a/mm/page_vma_mapped.c b/mm/page_vma_mapped.c
> index a4d52fdb3056..6559e17f11c2 100644
> --- a/mm/page_vma_mapped.c
> +++ b/mm/page_vma_mapped.c
> @@ -41,7 +41,7 @@ static bool map_pte(struct page_vma_mapped_walk *pvmw, pmd_t *pmdvalp,
> if (!pvmw->pte)
> return false;
>
> - ptent = ptep_get(pvmw->pte);
> + ptent = ptep_get_lockless(pvmw->pte);
>
> if (pte_none(ptent)) {
> return false;
> @@ -310,7 +310,7 @@ bool page_vma_mapped_walk(struct page_vma_mapped_walk *pvmw)
> goto restart;
> }
> pvmw->pte++;
> - } while (pte_none(ptep_get(pvmw->pte)));
> + } while (pte_none(ptep_get_lockless(pvmw->pte)));
>
Makes sense!
--
Cheers,
David
next prev parent reply other threads:[~2026-05-04 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 5:20 [PATCH] mm/page_vma_mapped_walk: add missing pgtable entry accessors Alexander Gordeev
2026-04-27 5:47 ` Anshuman Khandual
2026-04-27 8:40 ` Oscar Salvador
2026-04-27 8:49 ` Anshuman Khandual
2026-04-27 9:01 ` Alexander Gordeev
2026-04-27 9:02 ` David Hildenbrand (Arm)
2026-04-27 9:24 ` David Hildenbrand (Arm)
2026-04-29 13:47 ` Alexander Gordeev
2026-05-01 19:01 ` David Hildenbrand (Arm)
2026-05-03 6:51 ` Alexander Gordeev
2026-05-04 12:42 ` David Hildenbrand (Arm) [this message]
2026-04-30 12:11 ` kernel test robot
2026-05-02 4:54 ` kernel test robot
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=40ab8829-5f70-4474-9cf5-2c8da96d56d6@kernel.org \
--to=david@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=ljs@kernel.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