linux-kernel - Re: [PATCH] panic: remove redundant panic-cpu backtrace

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]

Message-ID: <84seichm5t.fsf@jogness.linutronix.de>
Date: Thu, 31 Jul 2025 09:15:02 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Sergey Senozhatsky <senozhatsky@...omium.org>, Andrew Morton
 <akpm@...ux-foundation.org>, Petr Mladek <pmladek@...e.com>
Cc: Feng Tang <feng.tang@...ux.alibaba.com>, linux-kernel@...r.kernel.org,
 Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH] panic: remove redundant panic-cpu backtrace

On 2025-07-31, Sergey Senozhatsky <senozhatsky@...omium.org> wrote:
> SYS_INFO_ALL_CPU_BT sends NMI backtrace request to
> all CPUs, which dumps an extra backtrace on panic CPU.

Isn't this only true if CONFIG_DEBUG_BUGVERBOSE=y?

Also, the information is not the same. trigger_all_cpu_backtrace() will
also dump the registers. For CONFIG_DEBUG_BUGVERBOSE=y on the panic CPU,
only the stack is dumped.

John Ogness