From: Zhenghui Hao <zhenghui.hao@qq.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] init, hugetlb: fix early parameter ordering
Date: Thu, 17 Sep 2026 14:28:35 +0800 [thread overview]
Message-ID: <tencent_58B1FA551DFC2B191C9848D394F023D21207@qq.com> (raw)
hugetlb records its command line parameters from early_param()
handlers and consumes them later from hugetlb_bootmem_alloc().
Commit d49004c5f0c1 ("arch, mm: consolidate initialization of nodes,
zones and memory map") moved that consumer into mm_core_init_early(),
which runs before the generic parse_early_param() call in
start_kernel(). Architectures that call parse_early_param() from
setup_arch() are not affected, but on parisc the parameters are then
recorded after they have already been consumed and are silently
dropped.
Patch 1/2 moves parse_early_param() before mm_core_init_early(),
together with jump_label_init() and static_call_init() so that the
"parameters may set static keys" guarantee still holds.
Patch 2/2 makes this class of ordering problem non-silent. It cannot
fire once 1/2 is applied; if you would rather take only the fix,
please drop 2/2.
Not tested on parisc hardware.
Zhenghui Hao (2):
init: parse early parameters before memory initialization
hugetlb: report cmdline parameters recorded too late
init/main.c | 8 ++++----
mm/hugetlb.c | 14 ++++++++++++++
2 files changed, 18 insertions(+), 4 deletions(-)
base-commit: 9b87fdc9af2fbfcdb5c24a64139685ef80f6573f
--
2.53.0
next reply other threads:[~2026-09-17 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 6:28 Zhenghui Hao [this message]
[not found] <20260917062837.558251-1-zhenghui.hao@qq.com>
2026-09-17 6:55 ` Zhenghui Hao
2026-09-17 7:41 ` Mike Rapoport
2026-09-17 9:19 ` zhenghui.hao
2026-09-17 9:45 ` Mike Rapoport
[not found] ` <tencent_B4700AD229B1E6D517FC751924185FD3BB07@qq.com>
2026-09-17 9:21 ` Mike Rapoport
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_58B1FA551DFC2B191C9848D394F023D21207@qq.com \
--to=zhenghui.hao@qq.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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®