From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Zi Yan <ziy@nvidia.com>, Matthew Brost <matthew.brost@intel.com>,
Joshua Hahn <joshua.hahnjy@gmail.com>,
Rakie Kim <rakie.kim@sk.com>, Byungchul Park <byungchul@sk.com>,
Gregory Price <gourry@gourry.net>,
Ying Huang <ying.huang@linux.alibaba.com>,
Alistair Popple <apopple@nvidia.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE
Date: Mon, 6 Jul 2026 20:30:29 +0200 [thread overview]
Message-ID: <892b2a73-4dbd-4090-89c5-46929530b855@kernel.org> (raw)
In-Reply-To: <20260706111958.3649651-1-wangkefeng.wang@huawei.com>
On 7/6/26 13:19, Kefeng Wang wrote:
> pte_pfn() and pte_dirty() have undefined behaviour when called on a
> non-present PTE. In migrate_vma_collect_pmd(), these functions may be
> invoked on non-present entries (e.g., swap PTEs), leading to potential
Certainly not real swap PTEs, as the previous function handling is
if (!pte_present(pte)) {
...
if (!softleaf_is_device_private(entry))
goto next;
Only device-private entries?
> crashes from pte_pfn() or incorrect dirty folio accounting from
> pte_dirty(). Fix both by guarding with pte_present() checks.
>
> Fixes: fd35ca3d12cc ("mm/migrate_device.c: copy pte dirty bit to page")
> Fixes: a3589e1d5fe3 ("mm/migrate_device.c: add missing flush_cache_page()")
I suspected device-private code, but indeed, these seem to be added afterwards.
But a3589e1d5fe3 only moved the flush_cache_page()? So that one seems wrong.
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> mm/migrate_device.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/migrate_device.c b/mm/migrate_device.c
> index 052167f9ad54..6e711381f092 100644
> --- a/mm/migrate_device.c
> +++ b/mm/migrate_device.c
> @@ -411,7 +411,8 @@ static int migrate_vma_collect_pmd(pmd_t *pmdp,
> bool anon_exclusive;
> pte_t swp_pte;
>
> - flush_cache_page(vma, addr, pte_pfn(pte));
> + if (pte_present(pte))
> + flush_cache_page(vma, addr, pte_pfn(pte));
> anon_exclusive = folio_test_anon(folio) &&
> PageAnonExclusive(page);
> if (anon_exclusive) {
> @@ -432,7 +433,7 @@ static int migrate_vma_collect_pmd(pmd_t *pmdp,
> migrate->cpages++;
>
> /* Set the dirty flag on the folio now the pte is gone. */
> - if (pte_dirty(pte))
> + if (pte_present(pte) && pte_dirty(pte))
> folio_mark_dirty(folio);
>
> /* Setup special migration page table entry */
Changes look good.
--
Cheers,
David
next prev parent reply other threads:[~2026-07-06 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 11:19 [PATCH] mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE Kefeng Wang
2026-07-06 18:01 ` Andrew Morton
2026-07-07 1:45 ` Zi Yan
2026-07-07 8:00 ` Kefeng Wang
2026-07-06 18:30 ` David Hildenbrand (Arm) [this message]
2026-07-07 1:28 ` Kefeng Wang
2026-07-07 7:04 ` David Hildenbrand (Arm)
2026-07-07 9:33 ` Kefeng Wang
2026-07-07 13:03 ` David Hildenbrand (Arm)
2026-07-07 14:20 ` Kefeng Wang
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=892b2a73-4dbd-4090-89c5-46929530b855@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=wangkefeng.wang@huawei.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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