From: jane.chu@oracle.com
To: Frank van der Linden <fvdl@google.com>,
akpm@linux-foundation.org, muchun.song@linux.dev,
linux-mm@kvack.org
Cc: osalvador@suse.de
Subject: Re: [PATCH] mm/hugetlb: copy the CMA flag when demoting
Date: Mon, 5 May 2025 10:02:46 -0700 [thread overview]
Message-ID: <dd64c016-be0c-4faf-bda1-9c84d29b51fd@oracle.com> (raw)
In-Reply-To: <20250501044325.20365-1-fvdl@google.com>
On 4/30/2025 9:43 PM, Frank van der Linden wrote:
> Since commit d2d786714080 ("mm/hugetlb: enable bootmem allocation
> from CMA areas"), a flag is used to mark hugetlb folios as allocated
> from CMA. This flag is also used to decide if it should be freed
> to CMA.
>
> However, the flag isn't copied to the smaller folios when a hugetlb
> folio is broken up for demotion, which would cause it to be freed
> incorrectly.
>
> Fix this by copying the flag to the smaller order hugetlb pages
> created from the original one.
>
> Fixes: d2d786714080 ("mm/hugetlb: enable bootmem allocation from CMA areas")
> Signed-off-by: Frank van der Linden <fvdl@google.com>
> ---
> mm/hugetlb.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index e3e6ac991b9c..6ea1be71aa42 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -4034,10 +4034,13 @@ static long demote_free_hugetlb_folios(struct hstate *src, struct hstate *dst,
>
> list_for_each_entry_safe(folio, next, src_list, lru) {
> int i;
> + bool cma;
>
> if (folio_test_hugetlb_vmemmap_optimized(folio))
> continue;
>
> + cma = folio_test_hugetlb_cma(folio);
> +
> list_del(&folio->lru);
>
> split_page_owner(&folio->page, huge_page_order(src), huge_page_order(dst));
> @@ -4053,6 +4056,9 @@ static long demote_free_hugetlb_folios(struct hstate *src, struct hstate *dst,
>
> new_folio->mapping = NULL;
> init_new_hugetlb_folio(dst, new_folio);
> + /* Copy the CMA flag so that it is freed correctly */
> + if (cma)
> + folio_set_hugetlb_cma(new_folio);
> list_add(&new_folio->lru, &dst_list);
> }
> }
Looks good.
Reviewed-by: Jane Chu <Jane.Chu@oracle.com>
thanks,
-jane
prev parent reply other threads:[~2025-05-05 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 4:43 Frank van der Linden
2025-05-02 7:17 ` Oscar Salvador
2025-05-02 8:27 ` Anshuman Khandual
2025-05-02 16:23 ` Frank van der Linden
2025-05-05 17:02 ` jane.chu [this message]
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=dd64c016-be0c-4faf-bda1-9c84d29b51fd@oracle.com \
--to=jane.chu@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=fvdl@google.com \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox