linux-kernel - Re: [PATCH] acpi/ghes: Make ghes_panic

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] [day] [month] [year] [list]

Message-ID: <1EA3C309-6508-489B-9F13-7659E8388A17@alien8.de>
Date: Fri, 27 Dec 2024 11:09:40 +0100
From: Borislav Petkov <bp@...en8.de>
To: Feng Tang <feng.tang@...ux.alibaba.com>, rafael@...nel.org,
 Len Brown <lenb@...nel.org>, James Morse <james.morse@....com>,
 Tony Luck <tony.luck@...el.com>, linux-acpi@...r.kernel.org,
 linux-kernel@...r.kernel.org
CC: Ira Weiny <ira.weiny@...el.com>, Dave Jiang <dave.jiang@...el.com>,
 Dan Williams <dan.j.williams@...el.com>, ying.huang@...ux.alibaba.com
Subject: Re: [PATCH] acpi/ghes: Make ghes_panic_timeout adjustable as a parameter

On December 27, 2024 10:54:22 AM GMT+01:00, Feng Tang <feng.tang@...ux.alibaba.com> wrote:
>There is a problem report that when debugging a hard-to-reproduce panic
>issue, user wanted the kernel to not reboot by adding "panic=0" in
>kernel cmdline, so that the panic context could be kept, say the panic
>was caught randomly in the mid-night, and user hoped to check it in
>the morning. GHES panic handler may overwrite that user setting and
>force to reboot after 'ghes_panic_timeout'(30) seconds.

Why doesn't the ghes panic handler honor a panic=0 setting?

-- 
Sent from a small device: formatting sucks and brevity is inevitable.