From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,osalvador@suse.de,muchun.song@linux.dev,mhocko@suse.com,linmiaohe@huawei.com,david@kernel.org,xialonglong@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-hugetlb-warn-instead-of-silently-bailing-gigantic-pages-without-runtime-support.patch removed from -mm tree
Date: Tue, 06 Oct 2026 17:49:40 -0700 [thread overview]
Message-ID: <20261007004941.2BBF31F0089D@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/hugetlb: warn instead of silently bailing gigantic pages without runtime support
has been removed from the -mm tree. Its filename was
mm-hugetlb-warn-instead-of-silently-bailing-gigantic-pages-without-runtime-support.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Longlong Xia <xialonglong@kylinos.cn>
Subject: mm/hugetlb: warn instead of silently bailing gigantic pages without runtime support
Date: Sun, 23 Aug 2026 12:40:52 +0800
remove_hugetlb_folio() and __update_and_free_hugetlb_folio() silently
return for gigantic hstates that lack runtime freeing support. All
callers should already filter such hstates upstream, so turn the silent
bail into a VM_WARN_ON_ONCE to catch caller regressions instead of masking
them.
Link: https://lore.kernel.org/20260823044118.1097121-3-xialonglong2025@163.com
Signed-off-by: Longlong Xia <xialonglong@kylinos.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Muchun Song <muchun.song@linux.dev>
Assisted-by: Codex:gpt-5.6-sol
Cc: David Hildenbrand <david@kernel.org>
Cc: Miaohe Lin <linmiaohe@huawei.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Oscar Salvador <osalvador@suse.de>
---
mm/hugetlb.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--- a/mm/hugetlb.c~mm-hugetlb-warn-instead-of-silently-bailing-gigantic-pages-without-runtime-support
+++ a/mm/hugetlb.c
@@ -1396,8 +1396,11 @@ void remove_hugetlb_folio(struct hstate
VM_BUG_ON_FOLIO(hugetlb_cgroup_from_folio_rsvd(folio), folio);
lockdep_assert_held(&hugetlb_lock);
- if (hstate_is_gigantic_no_runtime(h))
+ if (hstate_is_gigantic_no_runtime(h)) {
+ /* Callers must filter gigantic_no_runtime upstream. */
+ VM_WARN_ON_ONCE(1);
return;
+ }
list_del(&folio->lru);
@@ -1458,8 +1461,11 @@ static void __update_and_free_hugetlb_fo
{
bool clear_flag = folio_test_hugetlb_vmemmap_optimized(folio);
- if (hstate_is_gigantic_no_runtime(h))
+ if (hstate_is_gigantic_no_runtime(h)) {
+ /* Callers must filter gigantic_no_runtime upstream. */
+ VM_WARN_ON_ONCE(1);
return;
+ }
/*
* If we don't know which subpages are hwpoisoned, we can't free
_
Patches currently in -mm which might be from xialonglong@kylinos.cn are
mm-zswap-publish-the-initial-pool-with-list_add_rcu.patch
mm-zswap-enable-zswap_ever_enabled-in-zswap_pool_create.patch
reply other threads:[~2026-10-07 0:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261007004941.2BBF31F0089D@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=xialonglong@kylinos.cn \
/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.