[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d92202c8ec3d31eb54b41e669e3bf687acbf86e1.camel@gmx.de>
Date: Tue, 30 Sep 2025 19:35:09 +0200
From: Mike Galbraith <efault@....de>
To: Sebastian Siewior <bigeasy@...utronix.de>, John Ogness
<john.ogness@...utronix.de>
Cc: Calvin Owens <calvin@...nvd.org>, Breno Leitao <leitao@...ian.org>, Petr
Mladek <pmladek@...e.com>, Simon Horman <horms@...nel.org>,
kuba@...nel.org, Pavel Begunkov <asml.silence@...il.com>, Johannes Berg
<johannes@...solutions.net>, paulmck@...nel.org, LKML
<linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
boqun.feng@...il.com, Sergey Senozhatsky <senozhatsky@...omium.org>, Steven
Rostedt <rostedt@...dmis.org>
Subject: Re: netconsole: HARDIRQ-safe -> HARDIRQ-unsafe lock order warning
On Tue, 2025-09-30 at 16:30 +0200, Sebastian Siewior wrote:
> On 2025-09-30 16:29:02 [+0206], John Ogness wrote:
> > @bigeasy: You have some experience cleaning up this class of
> > problems. Any suggestions?
>
> I though that we have netconsole disabled on RT. As far as I remember it
> disables interrupts and expects that the NAPI callback (as in interrupts)
> will not fire not will there be any packets sent. So this is not going
> to work.
> It needs to be checked what kind of synchronisation is expected of
> netconsole by disabling interrupts and providing this by other means.
Oh dear. It's not netconsole at the root, it's the netpoll it's made
of. The xmit loops are trylock, but memory alloc/free issue remains,
as does netpoll xmit loops holding IRQs off for up to a tick.
I've been using a test coverage and monitoring patchlet for years that
let's RT relax local exclusion to better suit its needs, substituting
BH for IRQ exclusion. Due to meeting $subject, patchlet now does the
same whenever wireless nics are in use, as BH exclusion fits them too.
Not super pretty, but dirt simple and effective.
-Mike
Powered by blists - more mailing lists