From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Sunny Patel <nueralspacetech@gmail.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, linux-kernel@vger.kernel.org,
Balbir Singh <balbirs@nvidia.com>
Subject: Re: [PATCH] mm/migrate_device: fix double unlock and remove dead code
Date: Mon, 13 Apr 2026 21:38:44 +0200 [thread overview]
Message-ID: <7579105a-1261-45db-90ba-5e660d202b80@kernel.org> (raw)
In-Reply-To: <20260413130927.13263-1-nueralspacetech@gmail.com>
On 4/13/26 15:09, Sunny Patel wrote:
> Fix two bugs in device migration paths:
>
> 1) migrate_vma_collect_huge_pmd() calls spin_unlock after
> softleaf_entry_wait_on_locked(), which already releases the ptl.
>
> 2) migrate_vma_insert_huge_pmd_page() has a dead else-if branch and this
> branch is always unreachable.
>
Can you move 1) into a separate patch, add a Fixes: tag an CC stable?
I think it is
Fixes: a30b48bf1b24 ("mm/migrate_device: implement THP migration of zone
device pages")
2) will then be a pure cleanup patch.
Thanks!
> Signed-off-by: Sunny Patel <nueralspacetech@gmail.com>
> ---
> mm/migrate_device.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/mm/migrate_device.c b/mm/migrate_device.c
> index 8079676c8f1f..0e005c26ee88 100644
> --- a/mm/migrate_device.c
> +++ b/mm/migrate_device.c
> @@ -177,7 +177,6 @@ static int migrate_vma_collect_huge_pmd(pmd_t *pmdp, unsigned long start,
>
> if (softleaf_is_migration(entry)) {
> softleaf_entry_wait_on_locked(entry, ptl);
> - spin_unlock(ptl);
Yes, that looks correct to me.
> return -EAGAIN;
> }
>
> @@ -869,8 +868,7 @@ static int migrate_vma_insert_huge_pmd_page(struct migrate_vma *migrate,
> if (!is_huge_zero_pmd(*pmdp))
> goto unlock_abort;
> flush = true;
> - } else if (!pmd_none(*pmdp))
> - goto unlock_abort;
> + }
Huh, how did that happen. I hope that it's not a typo and we wanted to
check for something else.
--
Cheers,
David
next prev parent reply other threads:[~2026-04-13 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 13:09 Sunny Patel
2026-04-13 19:38 ` David Hildenbrand (Arm) [this message]
2026-04-13 20:03 ` Zi Yan
2026-04-13 22:21 ` Sunny Patel
2026-04-13 23:30 ` Matthew Brost
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=7579105a-1261-45db-90ba-5e660d202b80@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=byungchul@sk.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=nueralspacetech@gmail.com \
--cc=rakie.kim@sk.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