linux-kernel - Re: [PATCH v2 1/2] Handle flushing of CPU backtraces during 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87v80f2hii.fsf@jogness.linutronix.de>
Date: Mon, 05 Aug 2024 16:10:05 +0206
From: John Ogness <john.ogness@...utronix.de>
To: takakura@...inux.co.jp, pmladek@...e.com, rostedt@...dmis.org,
 senozhatsky@...omium.org, akpm@...ux-foundation.org, bhe@...hat.com,
 lukas@...ner.de, wangkefeng.wang@...wei.com, ubizjak@...il.com,
 feng.tang@...el.com, j.granados@...sung.com, stephen.s.brennan@...cle.com
Cc: linux-kernel@...r.kernel.org, nishimura@...inux.co.jp,
 taka@...inux.co.jp, Ryo Takakura <takakura@...inux.co.jp>
Subject: Re: [PATCH v2 1/2] Handle flushing of CPU backtraces during panic

On 2024-08-03, takakura@...inux.co.jp wrote:
> From: Ryo Takakura <takakura@...inux.co.jp>
>
> After panic, non-panicked CPU's has been unable to flush ringbuffer 
> while they can still write into it. This can affect CPU backtrace 
> triggered in panic only able to write into ringbuffer incapable of 
> flushing them.

Right now, they cannot write to it. If you apply your second patch
before this one, then the above statement is true.

Perhaps the ordering of the two patches should be reversed?

Either way, for the series:

Reviewed-by: John Ogness <john.ogness@...utronix.de>