From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Petr Mladek <pmladek@suse.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Tejun Heo <tj@kernel.org>,
Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [BUG] workqueues and printk not playing nice since next-20240130
Date: Mon, 5 Feb 2024 22:25:15 +0900 [thread overview]
Message-ID: <20240205132515.GF69174@google.com> (raw)
In-Reply-To: <ZcDdlRzpofn2cAuO@alley>
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.
next prev parent reply other threads:[~2024-02-05 13:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:04 [BUG] workqueues and printk not playing nice since next-20240130 Paul E. McKenney
2024-02-02 14:12 ` John Ogness
2024-02-02 15:58 ` Paul E. McKenney
2024-02-02 17:02 ` John Ogness
2024-02-02 17:35 ` Paul E. McKenney
2024-02-02 14:26 ` Jonas Oberhauser
2024-02-02 16:35 ` Paul E. McKenney
2024-02-02 16:56 ` Tejun Heo
2024-02-02 17:40 ` Paul E. McKenney
2024-02-05 13:07 ` Petr Mladek
2024-02-05 13:25 ` Sergey Senozhatsky [this message]
2024-02-05 17:45 ` Paul E. McKenney
2024-02-05 17:46 ` Tejun Heo
2024-02-05 19:41 ` Paul E. McKenney
2024-02-05 20:30 ` Tejun Heo
2024-02-05 21:17 ` Paul E. McKenney
2024-02-02 14:35 ` Petr Mladek
2024-02-02 16:07 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240205132515.GF69174@google.com \
--to=senozhatsky@chromium.org \
--cc=jiangshanlai@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=jonas.oberhauser@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox