From: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
To: "Brennan Lamoreaux (VMware)" <brennanlamoreaux@gmail.com>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: blamoreaux@vmware.com, frederic.martinsons@gmail.com,
vsirnapalli@vmware.com, amakhalov@vmware.com,
keerthanak@vmware.com, ankitja@vmware.com, bordoloih@vmware.com,
srivatsab@vmware.com, Daniel Wagner <wagi@monom.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 4.19-rt] workqueue: Fix deadlock due to recursive locking of pool->lock
Date: Tue, 28 Feb 2023 15:03:02 -0800 [thread overview]
Message-ID: <36f64ecf-89cb-3314-35d6-589569d58133@csail.mit.edu> (raw)
In-Reply-To: <20230228224938.88035-1-brennanlamoreaux@gmail.com>
On 2/28/23 2:49 PM, Brennan Lamoreaux (VMware) wrote:
> Upstream commit d8bb65ab70f7 ("workqueue: Use rcuwait for wq_manager_wait")
> replaced the waitqueue with rcuwait in the workqueue code. This change
> involved removing the acquisition of pool->lock in put_unbound_pool(),
> as it also adds the function wq_manager_inactive() which acquires this same
> lock and is called one line later as a parameter to rcu_wait_event().
>
> However, the backport of this commit in the PREEMPT_RT patchset
> 4.19.255-rt114 (patch 347) missed the removal of the acquisition of
> pool->lock in put_unbound_pool(). This leads to a deadlock due to
> recursive locking of pool->lock, as shown below in lockdep:
>
> [ 252.083713] WARNING: possible recursive locking detected
> [ 252.083718] 4.19.269-3.ph3-rt #1-photon Not tainted
> [ 252.083721] --------------------------------------------
> [ 252.083733] kworker/2:0/33 is trying to acquire lock:
> [ 252.083747] 000000000b7b1ceb (&pool->lock/1){....}, at:
> put_unbound_pool+0x10d/0x260
>
> [ 252.083857]
> but task is already holding lock:
> [ 252.083860] 000000000b7b1ceb (&pool->lock/1){....}, at:
> put_unbound_pool+0xbd/0x260
>
> [ 252.083876]
> other info that might help us debug this:
> [ 252.083897] Possible unsafe locking scenario:
>
> [ 252.083900] CPU0
> [ 252.083903] ----
> [ 252.083904] lock(&pool->lock/1);
> [ 252.083911] lock(&pool->lock/1);
> [ 252.083919]
> *** DEADLOCK ***
>
> [ 252.083921] May be due to missing lock nesting notation
>
> Fix this deadlock by removing the pool->lock acquisition in
> put_unbound_pool().
>
> Signed-off-by: Brennan Lamoreaux (VMware) <brennanlamoreaux@gmail.com>
> Cc: Daniel Wagner <wagi@monom.org>
> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Cc: Tejun Heo <tj@kernel.org>
Reviewed-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
> ---
> kernel/workqueue.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index a9f3cc02bdc1..55ebdd56a5de 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -3394,7 +3394,6 @@ static void put_unbound_pool(struct worker_pool *pool)
> * Because of how wq_manager_inactive() works, we will hold the
> * spinlock after a successful wait.
> */
> - raw_spin_lock_irq(&pool->lock);
> rcuwait_wait_event(&manager_wait, wq_manager_inactive(pool),
> TASK_UNINTERRUPTIBLE);
> pool->flags |= POOL_MANAGER_ACTIVE;
>
Regards,
Srivatsa
VMware Photon OS
next prev parent reply other threads:[~2023-02-28 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 22:49 Brennan Lamoreaux (VMware)
2023-02-28 23:03 ` Srivatsa S. Bhat [this message]
2023-03-13 9:36 ` Sebastian Andrzej Siewior
2023-03-16 7:08 ` Daniel Wagner
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=36f64ecf-89cb-3314-35d6-589569d58133@csail.mit.edu \
--to=srivatsa@csail.mit.edu \
--cc=amakhalov@vmware.com \
--cc=ankitja@vmware.com \
--cc=bigeasy@linutronix.de \
--cc=blamoreaux@vmware.com \
--cc=bordoloih@vmware.com \
--cc=brennanlamoreaux@gmail.com \
--cc=frederic.martinsons@gmail.com \
--cc=keerthanak@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=srivatsab@vmware.com \
--cc=tj@kernel.org \
--cc=vsirnapalli@vmware.com \
--cc=wagi@monom.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®