linux-kernel - Re: [PATCH printk v3 1/6] lib/nmi_backtrace: explicitly serialize banner and regs

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:   Thu, 24 Jun 2021 14:26:44 +0200
From:   Petr Mladek <pmladek@...e.com>
To:     John Ogness <john.ogness@...utronix.de>
Cc:     Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel@...r.kernel.org,
        "Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: [PATCH printk v3 1/6] lib/nmi_backtrace: explicitly serialize
 banner and regs

On Thu 2021-06-24 13:17:43, John Ogness wrote:
> Currently the nmi_backtrace is serialized against other CPUs because
> the messages are sent to the NMI buffers. Once these buffers are
> removed, only the dumped stack will be serialized against other CPUs
> (via the printk_cpu_lock).
> 
> Also serialize the nmi_backtrace banner and regs using the
> printk_cpu_lock so that per-CPU serialization will be preserved even
> after the NMI buffers are removed.
> 
> Signed-off-by: John Ogness <john.ogness@...utronix.de>

Reviewed-by: Petr Mladek <pmladek@...e.com>

Best Regards,
Petr