From: kernel test robot <oliver.sang@intel.com>
To: Yonghong Song <yhs@fb.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Kees Cook <keescook@chromium.org>,
Song Liu <song@kernel.org>, Zhen Lei <thunder.leizhen@huawei.com>,
Nick Desaulniers <ndesaulniers@google.com>,
<oliver.sang@intel.com>
Subject: [linus:master] [kallsyms] 8cc32a9bbf: Kernel_panic-not_syncing:stack-protector:Kernel_stack_is_corrupted_in:test_entry
Date: Wed, 23 Aug 2023 22:48:58 +0800 [thread overview]
Message-ID: <202308232200.1c932a90-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "Kernel_panic-not_syncing:stack-protector:Kernel_stack_is_corrupted_in:test_entry" on:
commit: 8cc32a9bbf2934d90762d9de0187adcb5ad46a11 ("kallsyms: strip LTO-only suffixes from promoted global functions")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master f7757129e3dea336c407551c98f50057c22bb266]
[test failed on linux-next/master 28c736b0e92e11bfe2b9997688213dc43cb22182]
in testcase: boot
compiler: clang-16
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202308232200.1c932a90-oliver.sang@intel.com
[ 28.923687][ T1] systemd[1]: RTC configured in localtime, applying delta of 0 minutes to system time.
[ 28.926842][ T1] systemd[1]: Failed to find module 'autofs4'
Welcome to Debian GNU/Linux 11 (bullseye)!
[ 30.135342][ T115] kallsyms_selftest: Test for 1153th symbol failed: (show_trace_log_lvl) addr=c1033b00
[ 30.135366][ T115] kallsyms_selftest: abort
[ 30.137440][ T115] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: test_entry+0x1419/0x1430
[ 30.138878][ T115] CPU: 0 PID: 115 Comm: kallsyms_test Tainted: G T 6.5.0-rc1-00002-g8cc32a9bbf29 #1
[ 30.140321][ T115] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 30.141688][ T115] Call Trace:
[ 30.142207][ T115] panic+0xf4/0x31c
[ 30.142789][ T115] __stack_chk_fail+0x10/0x10
[ 30.143470][ T115] ? test_entry+0x1419/0x1430
[ 30.144141][ T115] test_entry+0x1419/0x1430
[ 30.144802][ T115] ? __die_body+0xb0/0xb0
[ 30.145432][ T115] ? 0xc1000000
[ 30.145962][ T115] ? __die_body+0xb0/0xb0
[ 30.146642][ T115] kthread+0x203/0x220
[ 30.147262][ T115] ? sprint_backtrace_build_id+0x20/0x20
[ 30.148032][ T115] ? kthreadd+0x2f0/0x2f0
[ 30.148656][ T115] ret_from_fork+0x19/0x24
[ 30.149412][ T115] Kernel Offset: disabled
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230823/202308232200.1c932a90-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-23 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 14:48 kernel test robot [this message]
2023-08-24 20:25 ` [linus:master] [kallsyms] 8cc32a9bbf: Kernel_panic-not_syncing:stack-protector:Kernel_stack_is_corrupted_in:test_entry Kees Cook
2023-08-24 20:41 ` Yonghong Song
2023-08-24 20:52 ` Kees Cook
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=202308232200.1c932a90-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.com \
--cc=oe-lkp@lists.linux.dev \
--cc=song@kernel.org \
--cc=thunder.leizhen@huawei.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox