linux-kernel - [BUG REPORT] Triggering a panic in an x86 virtual machine does not wait

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 3 Jul 2023 11:44:26 +0800
From:   Baokun Li <libaokun1@...wei.com>
To:     <tglx@...utronix.de>
CC:     <arjan@...ux.intel.com>, <ashok.raj@...el.com>,
        <ashok.raj@...ux.intel.com>, <ebiederm@...ssion.com>,
        <linux-kernel@...r.kernel.org>, <mario.limonciello@....com>,
        <thomas.lendacky@....com>, <tony.luck@...el.com>,
        <tonyb@...ernetics.com>, <x86@...nel.org>,
        yangerkun <yangerkun@...wei.com>
Subject: [BUG REPORT] Triggering a panic in an x86 virtual machine does not
 wait

When I manually trigger panic in a qume x86 VM with

        `echo c > /proc/sysrq-trigger`,

  I find that the VM will probably reboot directly, but the 
PANIC_TIMEOUT is 0.
This prevents us from exporting the vmcore via panic, and even if we succeed
in panic exporting the vmcore, the processes in the vmcore are mostly
stop_this_cpu(). By dichotomizing we found the patch that introduced the
behavior change

    45e34c8af58f ("x86/smp: Put CPUs into INIT on shutdown if possible"),

can anyone help to see what is happening?

Thanks!
-- 
With Best Regards,
Baokun Li
.