From: Ard Biesheuvel <ardb@kernel.org>
To: Oliver Sang <oliver.sang@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [linus:master] [x86/sme] 48204aba80: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)
Date: Thu, 28 Mar 2024 08:54:38 +0200 [thread overview]
Message-ID: <CAMj1kXHYur1KVumT-n-8gF0jxBN606dwSHxk6fHCsrTYE+2mrg@mail.gmail.com> (raw)
In-Reply-To: <ZgUGtcJ1ZtQMhSHg@xsang-OptiPlex-9020>
On Thu, 28 Mar 2024 at 07:57, Oliver Sang <oliver.sang@intel.com> wrote:
>
...
> regarding this early-boot failure issue, by more tests, we double it may
> relate with 3 configs. as we shared in [1], they are set as below when the
> kernel run into early-boot failure:
>
> # CONFIG_INIT_STACK_NONE is not set
> CONFIG_INIT_STACK_ALL_ZERO=y
> CONFIG_GCC_PLUGIN_STACKLEAK=y
>
>
> the early-boot failure issue will _disappear_ by making either one of two
> changes:
>
> (1)
> CONFIG_CC_HAS_AUTO_VAR_INIT_ZERO=y
> -# CONFIG_INIT_STACK_NONE is not set
> +CONFIG_INIT_STACK_NONE=y
> # CONFIG_INIT_STACK_ALL_PATTERN is not set
> -CONFIG_INIT_STACK_ALL_ZERO=y
> +# CONFIG_INIT_STACK_ALL_ZERO is not set
> CONFIG_GCC_PLUGIN_STACKLEAK=y
>
>
> (2)
> CONFIG_INIT_STACK_ALL_ZERO=y
> -CONFIG_GCC_PLUGIN_STACKLEAK=y
> -# CONFIG_GCC_PLUGIN_STACKLEAK_VERBOSE is not set
> -CONFIG_STACKLEAK_TRACK_MIN_SIZE=100
> -# CONFIG_STACKLEAK_METRICS is not set
> -# CONFIG_STACKLEAK_RUNTIME_DISABLE is not set
> +# CONFIG_GCC_PLUGIN_STACKLEAK is not set
> CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
>
Thanks, this was very useful in narrowing it down. I sent out a fix
for the stackleak plugin.
prev parent reply other threads:[~2024-03-28 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 9:03 [linus:master] [x86/sme] 48204aba80: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) kernel test robot
2024-03-24 14:25 ` Borislav Petkov
2024-03-25 14:39 ` Ard Biesheuvel
2024-03-26 8:31 ` Oliver Sang
2024-03-26 8:59 ` Ard Biesheuvel
2024-03-28 5:57 ` Oliver Sang
2024-03-28 6:54 ` Ard Biesheuvel [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=CAMj1kXHYur1KVumT-n-8gF0jxBN606dwSHxk6fHCsrTYE+2mrg@mail.gmail.com \
--to=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=thomas.lendacky@amd.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 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.