From: Zhenghui Hao <zhenghui.hao@qq.com>
To: akpm@linux-foundation.org
Cc: vbabka@kernel.org, surenb@google.com, mhocko@suse.com,
brendan.jackman@linux.dev, hannes@cmpxchg.org, ziy@nvidia.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Zhenghui Hao <zhenghui.hao@qq.com>
Subject: [PATCH] mm/page_alloc: release isolated freepages on compound range mismatch
Date: Mon, 2 Nov 2026 17:06:44 +0800 [thread overview]
Message-ID: <tencent_869149E9C4305627F0ED654860AC4DDBC309@qq.com> (raw)
alloc_contig_frozen_range_noprof() isolates [outer_start, outer_end)
before checking whether a __GFP_COMP request exactly matches the
allocated range. If it does not, the function returns -EINVAL without
releasing cc.freepages, leaking the isolated pages.
Call release_free_list() before returning -EINVAL, while the pageblock
is still isolated, matching the cleanup already used when
isolate_freepages_range() fails.
Use WARN_ONCE() as well: the condition is reachable through the exported
API, and repeated invalid calls should not flood dmesg.
Tested with an order-9 free pageblock and a one-page __GFP_COMP
subrange:
before: free_buddy=0, leaked=512/512
after: free_buddy=1, leaked=0/512
Fixes: e98337d11bbdf ("mm/contig_alloc: support __GFP_COMP")
Signed-off-by: Zhenghui Hao <zhenghui.hao@qq.com>
---
mm/compaction.c | 2 +-
mm/internal.h | 2 ++
mm/page_alloc.c | 9 +++++++--
3 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/mm/compaction.c b/mm/compaction.c
index f1b2060eb201..11ec991206bb 100644
--- a/mm/compaction.c
+++ b/mm/compaction.c
@@ -89,7 +89,7 @@ static struct page *mark_allocated_noprof(struct page *page, unsigned int order,
}
#define mark_allocated(...) alloc_hooks(mark_allocated_noprof(__VA_ARGS__))
-static unsigned long release_free_list(struct list_head *freepages)
+unsigned long release_free_list(struct list_head *freepages)
{
int order;
unsigned long high_pfn = 0;
diff --git a/mm/internal.h b/mm/internal.h
index 566cbd2dce48..364b288a0e2c 100644
--- a/mm/internal.h
+++ b/mm/internal.h
@@ -880,6 +880,8 @@ int
isolate_migratepages_range(struct compact_control *cc,
unsigned long low_pfn, unsigned long end_pfn);
+unsigned long release_free_list(struct list_head *freepages);
+
#endif /* CONFIG_COMPACTION || CONFIG_CMA */
struct cma;
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index a8cac5e01066..6913e0f94540 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -7400,9 +7400,14 @@ int alloc_contig_frozen_range_noprof(unsigned long start, unsigned long end,
check_new_pages(head, order);
prep_new_page(head, order, gfp_mask, ALLOC_DEFAULT);
} else {
+ /*
+ * isolate_freepages_range() has removed the pages from the buddy
+ * allocator. Put them back before undoing pageblock isolation.
+ */
+ release_free_list(cc.freepages);
ret = -EINVAL;
- WARN(true, "PFN range: requested [%lu, %lu), allocated [%lu, %lu)\n",
- start, end, outer_start, outer_end);
+ WARN_ONCE(1, "PFN range: requested [%lu, %lu), allocated [%lu, %lu)\n",
+ start, end, outer_start, outer_end);
}
done:
undo_isolate_page_range(start, end);
--
2.53.0
next reply other threads:[~2026-11-02 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 9:06 Zhenghui Hao [this message]
2026-11-02 9:11 ` David Hildenbrand (Arm)
2026-11-02 9:29 ` Zhenghui Hao
2026-11-02 10:10 ` David Hildenbrand (Arm)
2026-11-02 14:30 ` Zi Yan
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=tencent_869149E9C4305627F0ED654860AC4DDBC309@qq.com \
--to=zhenghui.hao@qq.com \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--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
all inboxes | Powered by JetHome®