From: Tejun Heo <tj@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Jonas Oberhauser <jonas.oberhauser@huaweicloud.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
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 10:30:25 -1000 [thread overview]
Message-ID: <ZcFFYR-JOrfp7kvn@slm.duckdns.org> (raw)
In-Reply-To: <a8386e9d-39f6-4bd5-8329-30550fb2745a@paulmck-laptop>
Hello,
On Mon, Feb 05, 2024 at 11:41:10AM -0800, Paul E. McKenney wrote:
> [ 0.316453] ==================================================================
> [ 0.317646] BUG: KASAN: use-after-free in wq_update_node_max_active+0x123/0x810
> [ 0.318851] Read of size 8 at addr ffff88802109d788 by task swapper/0/0
Ah, that one is fixed by 15930da42f89 ("workqueue: Don't call
cpumask_test_cpu() with -1 CPU in wq_update_node_max_active()"). I have a
hard time imagining that having anything to do with console being quiet tho.
It's a cpumask bit test targeting cpu -1 and the result gets overwritten
later during boot.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-02-05 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:04 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
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 [this message]
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=ZcFFYR-JOrfp7kvn@slm.duckdns.org \
--to=tj@kernel.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=senozhatsky@chromium.org \
--cc=sfr@canb.auug.org.au \
/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
Powered by JetHome