linux-kernel - Re: netconsole: HARDIRQ-safe -> HARDIRQ-unsafe lock order warning

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

Message-ID: <fce0dffe6692b17eb41942d2fbb7c7aea05d8df0.camel@gmx.de>
Date: Thu, 21 Aug 2025 15:12:04 +0200
From: Mike Galbraith <efault@....de>
To: Breno Leitao <leitao@...ian.org>
Cc: Pavel Begunkov <asml.silence@...il.com>, Jakub Kicinski
 <kuba@...nel.org>,  Johannes Berg <johannes@...solutions.net>,
 paulmck@...nel.org, LKML <linux-kernel@...r.kernel.org>, 
 netdev@...r.kernel.org, boqun.feng@...il.com
Subject: Re: netconsole: HARDIRQ-safe -> HARDIRQ-unsafe lock order warning

On Thu, 2025-08-21 at 12:06 +0200, Mike Galbraith wrote:
> 
> A quick test proved you correct as to the why.

After a bit more testing/twiddling, seems NETCONSOLE_NBCON could
improve things at least a bit for RT. I was able to cleanly log an irq
thread handling sysrq-c over a wired interface.  That beats silence.

Wireless wants more than a wee twiddle w/wo RT or NETCONSOLE_NBCON. 
The path of least resistance there is bounce to kworker.  Oh well.

	-Mike