From: Ge Yang <yangge1116@126.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
21cnbao@gmail.com, david@redhat.com,
baolin.wang@linux.alibaba.com, muchun.song@linux.dev,
osalvador@suse.de, liuzixing@hygon.cn
Subject: Re: [PATCH V2] mm/hugetlb: wait for hugepage folios to be freed
Date: Tue, 18 Feb 2025 15:24:01 +0800 [thread overview]
Message-ID: <1ea2c7b0-790c-4f60-a713-9029252a0837@126.com> (raw)
In-Reply-To: <20250217203417.9689a271f792a4e23da322aa@linux-foundation.org>
在 2025/2/18 12:34, Andrew Morton 写道:
> On Sat, 15 Feb 2025 15:20:26 +0800 yangge1116@126.com wrote:
>
>> From: Ge Yang <yangge1116@126.com>
>>
>> Since the introduction of commit b65d4adbc0f0 ("mm: hugetlb: defer freeing
>> of HugeTLB pages"), which supports deferring the freeing of HugeTLB pages,
>> the allocation of contiguous memory through cma_alloc() may fail
>> probabilistically.
>>
>> In the CMA allocation process, if it is found that the CMA area is occupied
>> by in-use hugepage folios, these in-use hugepage folios need to be migrated
>> to another location. When there are no available hugepage folios in the
>> free HugeTLB pool during the migration of in-use HugeTLB pages, new folios
>> are allocated from the buddy system. A temporary state is set on the newly
>> allocated folio. Upon completion of the hugepage folio migration, the
>> temporary state is transferred from the new folios to the old folios.
>> Normally, when the old folios with the temporary state are freed, it is
>> directly released back to the buddy system. However, due to the deferred
>> freeing of HugeTLB pages, the PageBuddy() check fails, ultimately leading
>> to the failure of cma_alloc().
>>
>> Here is a simplified call trace illustrating the process:
>> cma_alloc()
>> ->__alloc_contig_migrate_range() // Migrate in-use hugepage
>> ->unmap_and_move_huge_page()
>> ->folio_putback_hugetlb() // Free old folios
>> ->test_pages_isolated()
>> ->__test_page_isolated_in_pageblock()
>> ->PageBuddy(page) // Check if the page is in buddy
>>
>> To resolve this issue, we have implemented a function named
>> wait_for_hugepage_folios_freed(). This function ensures that the hugepage
>> folios are properly released back to the buddy system after their migration
>> is completed. By invoking wait_for_hugepage_folios_freed() before calling
>> PageBuddy(), we ensure that PageBuddy() will succeed.
>>
>> Fixes: b65d4adbc0f0 ("mm: hugetlb: defer freeing of HugeTLB pages")
>
> Do you feel that this issue is serious enough to justify a -stable
> backport of the fix?
Yes, I will add 'CC: stable@vger.kernel.org' in the next patch, thanks.
next prev parent reply other threads:[~2025-02-18 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 7:20 [PATCH V2] mm/hugetlb: wait for hugepage folios to be freed yangge1116
2025-02-18 4:34 ` Andrew Morton
2025-02-18 7:24 ` Ge Yang [this message]
2025-02-18 6:52 ` Muchun Song
2025-02-18 8:52 ` David Hildenbrand
2025-02-18 9:06 ` Ge Yang
2025-02-18 7:05 ` Muchun Song
2025-02-18 7:25 ` Ge Yang
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=1ea2c7b0-790c-4f60-a713-9029252a0837@126.com \
--to=yangge1116@126.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuzixing@hygon.cn \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.