Re: [BUG] workqueues and printk not playing nice since next-20240130

[Tejun Heo]

On Mon, Feb 05, 2024 at 09:45:53AM -0800, Paul E. McKenney wrote:
> On Mon, Feb 05, 2024 at 10:25:15PM +0900, Sergey Senozhatsky wrote:
> > On (24/02/05 14:07), Petr Mladek wrote:
> > > > Good point, if it does recur, I could try it on bare metal.
> > > 
> > > Please, me, John, and Sergey know if anyone see this again. I do not
> > > feel comfortable when there is problem which might make consoles calm.
> > 
> > Agreed.
> > 
> > > Bisection identified this commit:
> > > 5797b1c18919 ("workqueue: Implement system-wide nr_active enforcement for unbound workqueues")
> > 
> > That commit triggered early boot use-after-free (per kasan) on
> > my system, which probably could derail some things.
> 
> And enabling KASAN on next-20240130 got me that same KASAN report and
> also suppressed the misbehavior, which is not surprising given that
> KASAN quarantines free memory for some time.  Plus enabling KASAN
> on recent -next does not trigger that KASAN report.
> 
> So my guess is that we can attribute my oddball test failures to
> that use after free.  But I will of course continue testing.

Can someone paste the KASAN report?

Thanks.

-- 
tejun