From: Lance Yang <lance.yang@linux.dev>
To: usama.arif@linux.dev
Cc: akpm@linux-foundation.org, apopple@nvidia.com, byungchul@sk.com,
david@kernel.org, gourry@gourry.net, joshua.hahnjy@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
matthew.brost@intel.com, rakie.kim@sk.com,
ying.huang@linux.alibaba.com, ziy@nvidia.com,
shakeel.butt@linux.dev, hannes@cmpxchg.org, kernel-team@meta.com,
sashiko-bot@kernel.org, Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH] mm/migrate_device: pin large folios before splitting
Date: Thu, 2 Jul 2026 12:45:05 +0800 [thread overview]
Message-ID: <20260702044505.98105-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260701140638.840773-1-usama.arif@linux.dev>
On Wed, Jul 01, 2026 at 07:06:38AM -0700, Usama Arif wrote:
>migrate_vma_collect_pmd() can detect a large folio while holding the PTE
>lock, then drop the PTE lock before calling migrate_vma_split_folio(). The
>split helper took its own reference, but only after the lock had already
>been dropped.
>
>One way to hit this is device migration over a range that contains a large
>folio. The walker reads the PTE while holding the PTE lock and derives the
>folio either from a present PTE via vm_normal_page(), or from a non-present
>PTE that encodes a device-private softleaf entry. It then has to drop the
>PTE lock because split_folio() can block. Before migrate_vma_split_folio()
>gets a folio reference, concurrent reclaim, migration, or truncation can
>replace or clear the entry and drop the last reference to the folio. The
>split helper would then take a reference and lock on a stale folio pointer.
>
>Take a temporary reference before dropping the PTE lock and pass that
>reference into migrate_vma_split_folio(). The helper consumes the
>reference, so split_folio() still sees only the expected caller pin instead
>of an extra pin that could make the split fail.
Yeah, that's how it should have been:
lookup under PTL -> get folio ref -> drop PTL.
Getting a ref after dropping PTL feels a bit too optimistic ...
>Reported-by: sashiko-bot <sashiko-bot@kernel.org>
>Link: https://sashiko.dev/#/patchset/20260630164143.1595669-1-usama.arif%40linux.dev
>Fixes: 022a12deda53 ("mm/migrate_device: handle partially mapped folios during collection")
>Signed-off-by: Usama Arif <usama.arif@linux.dev>
>---
Thanks for fixing it! Feel free to add:
Reviewed-by: Lance Yang <lance.yang@linux.dev>
next prev parent reply other threads:[~2026-07-02 4:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 14:06 [PATCH] mm/migrate_device: pin large folios before splitting Usama Arif
2026-07-01 16:49 ` David Hildenbrand (Arm)
2026-07-01 17:02 ` Zi Yan
2026-07-01 19:27 ` Andrew Morton
2026-07-01 20:06 ` David Hildenbrand (Arm)
2026-07-01 20:16 ` Zi Yan
2026-07-02 0:33 ` Alistair Popple
2026-07-02 7:59 ` David Hildenbrand (Arm)
2026-07-01 23:29 ` SJ Park
2026-07-02 10:47 ` Usama Arif
2026-07-02 4:45 ` Lance Yang [this message]
2026-07-02 10:56 ` Usama Arif
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=20260702044505.98105-1-lance.yang@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=sashiko-bot@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=usama.arif@linux.dev \
--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