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

[Mike Galbraith <efault@gmx.de>]

On Mon, 2025-09-08 at 13:27 -0700, Calvin Owens wrote:
> On Friday 09/05 at 14:54 +0206, John Ogness wrote:
> > <snip>
> > 
> > NBCON is meant to deprecate @oops_in_progress. However, it is true that
> > consoles not implementing ->write_atomic() will never print panic
> > output.
> 
> Below is a silly little testcase that makes it more convenient to test
> if crashes are getting out in a few canned cases, in case anyone else
> finds it useful.

I gave it a go.

> Testing this on 6.17-rc5 on a Pi 4b, I don't get any netconsole output
> at all for any crash case over wifi, so that already doesn't work. All
> the cases currently work over ethernet.

With local hackery on top of Breno's patches I captured all testcases
for RT and !RT wired and wireless except for one RT wired instance due
to a GPF_ATOMIC allocation failure.

The wireless stack was unhappy about ending up in an nbcon write_atomic
method with IRQs disabled, thus sent complaints along with the oopsen.

	-Mike