From: David Hildenbrand <david@redhat.com>
To: Dev Jain <dev.jain@arm.com>, akpm@linux-foundation.org
Cc: ziy@nvidia.com, baolin.wang@linux.alibaba.com,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, baohua@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] khugepaged: Reduce race probability between migration and khugepaged
Date: Thu, 3 Jul 2025 11:25:52 +0200 [thread overview]
Message-ID: <1d82c930-be52-4983-9fd7-099df487eb48@redhat.com> (raw)
In-Reply-To: <20250703054823.49149-1-dev.jain@arm.com>
On 03.07.25 07:48, Dev Jain wrote:
> Suppose a folio is under migration, and khugepaged is also trying to
> collapse it. collapse_pte_mapped_thp() will retrieve the folio from the
> page cache via filemap_lock_folio(), thus taking a reference on the folio
> and sleeping on the folio lock, since the lock is held by the migration
> path. Migration will then fail in
> __folio_migrate_mapping -> folio_ref_freeze. Reduce the probability of
> such a race happening (leading to migration failure) by bailing out
> if we detect a PMD is marked with a migration entry.
>
> This fixes the migration-shared-anon-thp testcase failure on Apple M3.
>
> Note that, this is not a "fix" since it only reduces the chance of
> interference of khugepaged with migration, wherein both the kernel
> functionalities are deemed "best-effort".
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
>
> v1->v2:
> - Remove SCAN_PMD_MIGRATION, merge into SCAN_PMD_MAPPED (David, Anshuman)
> - Add a comment (Lorenzo)
>
> v1:
> - https://lore.kernel.org/all/20250630044837.4675-1-dev.jain@arm.com/
>
> mm/khugepaged.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 1aa7ca67c756..3fdefc4f4984 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -941,6 +941,15 @@ static inline int check_pmd_state(pmd_t *pmd)
>
> if (pmd_none(pmde))
> return SCAN_PMD_NONE;
> +
> + /*
> + * The folio may be under migration when khugepaged is trying to
> + * collapse it. Migration success or failure will eventually end
> + * up with the PMD still pointing to a PMD-order folio, so return
> + * SCAN_PMD_MAPPED.
Nit: the last part (, so return ..) is obvious from the code.
I would have written
/*
* The folio may be under migration when khugepaged is trying to
* collapse it. Migration success or failure will eventually end
* up with a present PMD entry again.
*/
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-03 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 5:48 [PATCH v2] khugepaged: Reduce race probability between migration and khugepaged Dev Jain
2025-07-03 9:25 ` David Hildenbrand [this message]
2025-07-03 9:40 ` Anshuman Khandual
2025-07-03 9:52 ` Dev Jain
2025-07-03 10:09 ` David Hildenbrand
2025-07-03 10:27 ` Dev Jain
2025-07-03 9:41 ` Oscar Salvador
2025-07-03 14:07 ` Zi Yan
2025-07-04 3:27 ` Baolin 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=1d82c930-be52-4983-9fd7-099df487eb48@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.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;
as well as URLs for NNTP newsgroup(s).