From: "Paul E. McKenney" <paulmck@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] workqueue: Fix hotplug races
Date: Tue, 30 Nov 2021 10:01:03 -0800 [thread overview]
Message-ID: <20211130180103.GV641268@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20211130000612.591368-1-frederic@kernel.org>
On Tue, Nov 30, 2021 at 01:06:10AM +0100, Frederic Weisbecker wrote:
> While triggering rcutorture splats, I couldn't trace down to the exact
> cause due to the issue being tracing-unfriendly. But looking at the code,
> those two potential races look like plausible causes and also after
> these two patches, I couldn't reproduce the rcutorture issues again (yet...).
>
> Frederic Weisbecker (2):
> workqueue: Fix unbind_workers() VS wq_worker_running() race
> workqueue: Fix unbind_workers() VS wq_worker_sleeping() race
>
> kernel/workqueue.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
This series passed 1500 hours of TREE01 with rcupdate.rcu_expedited=1
and also with Frederic's fix for expedited RCU grace periods, so:
Tested-by: Paul E. McKenney <paulmck@kernel.org>
Thanx, Paul
prev parent reply other threads:[~2021-11-30 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 0:06 Frederic Weisbecker
2021-11-30 0:06 ` [RFC PATCH 1/2] workqueue: Fix unbind_workers() VS wq_worker_running() race Frederic Weisbecker
2021-11-30 0:33 ` Lai Jiangshan
2021-11-30 0:06 ` [RFC PATCH 2/2] workqueue: Fix unbind_workers() VS wq_worker_sleeping() race Frederic Weisbecker
2021-11-30 0:57 ` Lai Jiangshan
2021-11-30 16:36 ` [RFC PATCH 0/2] workqueue: Fix hotplug races Tejun Heo
2021-12-01 14:48 ` Frederic Weisbecker
2021-11-30 18:01 ` Paul E. McKenney [this message]
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=20211130180103.GV641268@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®