linux-kernel - Re: [PATCH v2] 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: <i4hhb2kxilkrzdnddffqrmyauekwmj5cztpxplutcldaktgiq7@ksorrmedmnk7>
Date: Thu, 4 Sep 2025 11:34:27 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, 
	John Ogness <john.ogness@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org>, 
	Feng Tang <feng.tang@...ux.alibaba.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] panic: Remove redundant panic-cpu backtrace

On (25/09/03 12:04), Petr Mladek wrote:
> Backtraces from all CPUs are printed during panic() when
> SYS_INFO_ALL_CPU_BT is set. It shows the backtrace for
> the panic-CPU even when it has already been explicitly
> printed before.
> 
> Do not change the legacy code which prints the backtrace
> in various context, for example, as part of Oops report,
> right after panic message. It will always be visible in
> the crash dump.
> 
> Instead, remember when the backtrace was printed, and skip
> it when dumping the optional backtraces on all CPUs.
> 
> Signed-off-by: Sergey Senozhatsky <senozhatsky@...omium.org>

That's very kind of you, Petr.  Thanks for working on this.


// As a side note, my involvement was more of a
// Reported-and-tested-by: Sergey Senozhatsky <senozhatsky@...omium.org>
// Petr is the sole author of this patch.