[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240205132515.GF69174@google.com>
Date: Mon, 5 Feb 2024 22:25:15 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Petr Mladek <pmladek@...e.com>
Cc: "Paul E. McKenney" <paulmck@...nel.org>, Tejun Heo <tj@...nel.org>,
Jonas Oberhauser <jonas.oberhauser@...weicloud.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-kernel@...r.kernel.org, rcu@...r.kernel.org
Subject: Re: [BUG] workqueues and printk not playing nice since next-20240130
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.
Powered by blists - more mailing lists