From: Yin Fengwei <fengwei.yin@intel.com>
To: Borislav Petkov <bp@suse.de>, Carel Si <beibei.si@intel.com>
Cc: Joerg Roedel <jroedel@suse.de>,
LKML <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<lkp@lists.01.org>, <lkp@intel.com>
Subject: Re: [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage
Date: Thu, 16 Dec 2021 15:04:16 +0800 [thread overview]
Message-ID: <009391a5-468b-2a5d-1f12-44d2e3104bd6@intel.com> (raw)
In-Reply-To: <Ybm96seTxl+pWjTX@zn.tnic>
Hi Boris,
On 12/15/2021 6:05 PM, Borislav Petkov wrote:
> On Wed, Dec 15, 2021 at 03:00:13PM +0800, Carel Si wrote:
>> We have verified by hand, still can reproduce this issue.
>
> Ok, please give details how exactly you reproduce: host, guest, kernel
> versions, configs, machine types, i.e., /proc/cpuinfo, dmesg, etc. I'd
> like to see if I can find a similar machine here.
>
> Also, would it be possible to upload your vmlinuz somewhere so that I
> can download it for testing?
The testing was with Qemu. And we found that the hang is related with
clang-14.
The original report showed the kernel is built with clang-14:
# build kernel
cd linux
cp config-5.16.0-rc3-00003-gf154f290855b .config
make HOSTCC=clang-14 CC=clang-14 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage modules
make HOSTCC=clang-14 CC=clang-14 ARCH=x86_64 INSTALL_MOD_PATH=<mod-install-dir> modules_install
And the clang-14 generate different code comparing to clang-11. I pasted
the native_write_cr4 assembly code generated with clang-14 and clang-11 to:
https://zerobin.net/?ced930258536c677#U6et+H97oxbpdYclFvAX0F3ha0rCJctLE53mJjDKrgo=
The extra code generated by clang-14 is like:
ffffffff810b8784: 48 89 d8 mov %rbx,%rax
ffffffff810b8787: 48 c1 e8 03 shr $0x3,%rax
ffffffff810b878b: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
ffffffff810b8792: fc ff df
ffffffff810b8795: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1)
--> Qemu reboot after this instruction from x86_64_start_kernel
ffffffff810b8799: 74 08 je ffffffff810b87a3 <native_write_cr4+0x84>
ffffffff810b879b: 48 89 df mov %rbx,%rdi
ffffffff810b879e: e8 cc 7c 64 00 callq ffffffff8170046f <__asan_report_load8_noabort>
ffffffff810b87a3: 48 ff 03 incq (%rbx)
ffffffff810b87a6: 5b pop %rbx
Looks like KASAN related stub generated by clang-14 (KASAN_SHADOW_OFFSET and asan_report).
This function is early function called before kasan_init.
Looks like we need to disable KASAN_SANITIZE for arch/x86/kernel/cpu/common.c. So clang-14 will
be happy with this kind of early TLB flush? Thanks.
Regards
Yin, Fengwei
>
> Thx.
>
next prev parent reply other threads:[~2021-12-16 7:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 14:41 [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage kernel test robot
2021-12-14 16:38 ` Borislav Petkov
2021-12-15 7:00 ` [LKP] " Carel Si
2021-12-15 10:05 ` Borislav Petkov
2021-12-16 7:04 ` Yin Fengwei [this message]
2021-12-16 10:06 ` Borislav Petkov
2021-12-16 11:58 ` Carel Si
2021-12-16 12:21 ` Yin Fengwei
2021-12-17 12:52 ` [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV? Borislav Petkov
2021-12-17 18:04 ` Nathan Chancellor
2021-12-18 11:00 ` Borislav Petkov
2021-12-20 11:00 ` [PATCH] x86/mm: Prevent early boot triple-faults with instrumentation Borislav Petkov
2021-12-18 10:39 ` [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV? Yin Fengwei
2021-12-18 11:01 ` Borislav Petkov
2021-12-20 1:51 ` Yin Fengwei
2021-12-21 14:31 ` Carel Si
2021-12-21 15:10 ` Marco Elver
2021-12-21 15:22 ` Borislav Petkov
2022-01-05 2:35 ` Yin Fengwei
2022-01-05 11:36 ` Borislav Petkov
2022-01-05 12:47 ` Yin Fengwei
2022-01-05 15:21 ` Borislav Petkov
2022-01-06 6:56 ` Yin Fengwei
2021-12-21 15:14 ` Borislav Petkov
2021-12-22 10:59 ` [tip: x86/mm] x86/mm: Prevent early boot triple-faults with instrumentation tip-bot2 for Borislav Petkov
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=009391a5-468b-2a5d-1f12-44d2e3104bd6@intel.com \
--to=fengwei.yin@intel.com \
--cc=beibei.si@intel.com \
--cc=bp@suse.de \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=x86@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