[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250930143059.OA_NFC9S@linutronix.de>
Date: Tue, 30 Sep 2025 16:30:59 +0200
From: Sebastian Siewior <bigeasy@...utronix.de>
To: John Ogness <john.ogness@...utronix.de>
Cc: Calvin Owens <calvin@...nvd.org>, Breno Leitao <leitao@...ian.org>,
Petr Mladek <pmladek@...e.com>, Mike Galbraith <efault@....de>,
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 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.
> John Ogness
Sebastian
Powered by blists - more mailing lists