From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Pu Lehui <pulehui@huawei.com>
Subject: Re: [PATCH] mm: use proper PTE accessor in move_ptes()
Date: Thu, 30 Jul 2026 15:08:04 +0200 [thread overview]
Message-ID: <51102823-ceab-499f-8b6a-162e392f864f@kernel.org> (raw)
In-Reply-To: <7f60a20f-7293-489b-8539-847fa1b96789@kernel.org>
On 7/30/26 15:07, David Hildenbrand (Arm) wrote:
> On 7/20/26 16:16, Alexander Gordeev wrote:
>> Follow the pattern established by commit c33c794828f2
>> ("mm: ptep_get() conversion") and use the proper PTE
>> accessor instead of a direct pointer dereference.
>>
>> Fixes: b36b701bbcd9 ("mm: expose abnormal new_pte during move_ptes")
>> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
>> ---
>> mm/mremap.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/mremap.c b/mm/mremap.c
>> index 0dfe3de39ccc..e99b19a9850b 100644
>> --- a/mm/mremap.c
>> +++ b/mm/mremap.c
>> @@ -264,7 +264,7 @@ static int move_ptes(struct pagetable_move_control *pmc,
>>
>> for (; old_addr < old_end; old_ptep += nr_ptes, old_addr += nr_ptes * PAGE_SIZE,
>> new_ptep += nr_ptes, new_addr += nr_ptes * PAGE_SIZE) {
>> - VM_WARN_ON_ONCE(!pte_none(*new_ptep));
>> + VM_WARN_ON_ONCE(!pte_none(ptep_get(new_ptep)));
>>
>> nr_ptes = 1;
>> max_nr_ptes = (old_end - old_addr) >> PAGE_SHIFT;
>
> Acked-by: David Hildenbrand (Arm) <david@kernel.org>
>
Ah, but I think we should drop the Fixes: tag, or am I missing something?
--
Cheers,
David
next prev parent reply other threads:[~2026-07-30 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 14:16 Alexander Gordeev
2026-07-30 11:41 ` Usama Anjum
2026-07-30 13:07 ` David Hildenbrand (Arm)
2026-07-30 13:08 ` David Hildenbrand (Arm) [this message]
2026-07-30 14:50 ` Alexander Gordeev
2026-07-30 17:06 ` David Hildenbrand (Arm)
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=51102823-ceab-499f-8b6a-162e392f864f@kernel.org \
--to=david@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pulehui@huawei.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
all inboxes | Powered by JetHome®