linux-kernel - [PATCH printk 0/1] alternate fix for nbcon_cpu_emergency

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

Message-Id: <20240719134818.3311665-1-john.ogness@linutronix.de>
Date: Fri, 19 Jul 2024 15:54:17 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Petr Mladek <pmladek@...e.com>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org,
	Juri Lelli <juri.lelli@...hat.com>
Subject: [PATCH printk 0/1] alternate fix for nbcon_cpu_emergency_flush()

Hi Petr,

Currently in linux-next we have commit b955f0eead54 ("printk: nbcon:
Fix nbcon_cpu_emergency_flush() when preemptible"). But as you
pointed out [0], there is no need to disable preemption at all if
we only need to know if the current CPU is in emergency state.

Here is an alternative patch that correctly addresses the issue by
avoiding the migration checks.

Since the previous patch is not yet mainline, perhaps you want to
use this one instead in order to avoid a revert. Up to you.

John Ogness

[0] https://lore.kernel.org/lkml/Zn7b8g1HtuTIAwyi@pathway.suse.cz

John Ogness (1):
  printk: nbcon: do not require migration disabled for
    nbcon_get_cpu_emergency_nesting()

 kernel/printk/nbcon.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

base-commit: c51cf7315db1392af58b909d1004133f6dbf0bf6
-- 
2.39.2