From: Breno Leitao <leitao@debian.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [trace:bootconfig/for-next 16/16] init/main.c:437:20: warning: stack frame size (4192) exceeds limit (2048) in 'bootconfig_apply_early_params'
Date: Wed, 25 Mar 2026 02:55:35 -0700 [thread overview]
Message-ID: <acOw2YXMZZEQ1UUz@gmail.com> (raw)
In-Reply-To: <20260325155227.55cdfb9f4ce96c335d0c7f18@kernel.org>
On Wed, Mar 25, 2026 at 03:52:27PM +0900, Masami Hiramatsu wrote:
> > > 437 static void __init bootconfig_apply_early_params(void)
> > 438 {
> > 439 char val_buf[COMMAND_LINE_SIZE];
>
> Ah, this COMMAND_LINE_SIZE is too big to allocate it on stack.
> We need to make it as a static __initdata variable.
Ack, I will respin it. Thanks!
> Thank you,
>
> > 440 struct xbc_node *knode, *root;
> > 441 const char *val;
> > 442
> > 443 root = xbc_find_node("kernel");
> > 444 if (!root)
> > 445 return;
> > 446
> > 447 /*
> > 448 * Keys that do not match any early_param() handler are silently
> > 449 * ignored — do_early_param() always returns 0.
> > 450 */
> > 451 xbc_node_for_each_key_value(root, knode, val) {
> > 452 if (xbc_node_compose_key_after(root, knode, xbc_namebuf, XBC_KEYLEN_MAX) < 0)
> > 453 continue;
> > 454
> > 455 if (!val) {
I also found that val cannot be NULL here, given
xbc_node_for_each_key_value() returns an empty string ("") instead of
NULL, so, I will remove this branch here as well.
prev parent reply other threads:[~2026-03-25 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 2:37 [trace:bootconfig/for-next 16/16] init/main.c:437:20: warning: stack frame size (4192) exceeds limit (2048) in 'bootconfig_apply_early_params' kernel test robot
2026-03-25 6:52 ` Masami Hiramatsu
2026-03-25 9:55 ` Breno Leitao [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=acOw2YXMZZEQ1UUz@gmail.com \
--to=leitao@debian.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.