From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com, Brett A C Sheffield <bacs@librecast.net>
Subject: Re: [PATCH 6.12 0000/1102] 6.12.111-rc1 review
Date: Fri, 18 Sep 2026 11:54:03 -0400 [thread overview]
Message-ID: <20260918151136.2101477301-sashal@kernel.org> (raw)
In-Reply-To: <aqxBBu5GXVhHcqTz@auntie.librecast.net>
On Thu, Sep 17, 2026 at 07:35:34PM +0000, Brett A C Sheffield wrote:
> 6.12.111-rc1 hangs on boot on this machine (AMD Ryzen 9 9950X).
[...]
> # first 'bad' commit: [22ae428b0045981bd19f8c75f700a67198062f32]
> mm/hugetlb: initialize gigantic bootmem hugepage struct pages earlier
Thanks for the bisect, it lands exactly on the problem. Dropped from the
6.12 queue:
b1b7c045e808 ("mm/hugetlb: initialize gigantic bootmem hugepage
struct pages earlier")
For the record, why it breaks only on 6.12: the backport moves
gather_bootmem_prealloc() out of hugetlb_init() (a subsys_initcall) into
page_alloc_init_late(), which runs well before do_basic_setup(). Upstream that
reordering is safe because since v6.15 the per-node huge_boot_pages[] list
heads are initialized unconditionally and very early in
hugetlb_bootmem_alloc(). 6.12 has neither that function nor the commits that
added it, so the only INIT_LIST_HEAD() of those lists is the lazy loop in
hugetlb_hstate_alloc_pages(), reached early only when a gigantic hugepage is
requested on the command line. Boot a CONFIG_HUGETLB_PAGE=y kernel without
hugepagesz=/hugepages= and the relocated code walks an all-zero list head, so
the first iteration dereferences NULL.
Nothing else in the queue depended on it, so it comes out on its own.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-18 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 14:59 Greg Kroah-Hartman
2026-09-17 16:57 ` Florian Fainelli
2026-09-17 19:11 ` Peter Schneider
2026-09-17 20:21 ` Pavel Machek
2026-09-18 15:54 ` Sasha Levin
2026-09-17 19:35 ` Brett A C Sheffield
2026-09-17 20:19 ` Peter Schneider
2026-09-18 5:49 ` Peter Schneider
2026-09-18 15:54 ` Sasha Levin
2026-09-18 15:54 ` Sasha Levin
2026-09-18 15:54 ` Sasha Levin [this message]
2026-09-17 20:18 ` Pavel Machek
2026-09-18 11:27 ` Jon Hunter
2026-09-18 15:54 ` Sasha Levin
2026-09-18 15:54 ` Sasha Levin
2026-09-18 7:16 ` [PATCH 6.18 0000/1250] 6.18.53-rc1 review Wentao Guan
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=20260918151136.2101477301-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=bacs@librecast.net \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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®