[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230313093641.pxvwFHCJ@linutronix.de>
Date: Mon, 13 Mar 2023 10:36:41 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Brennan Lamoreaux (VMware)" <brennanlamoreaux@...il.com>,
Daniel Wagner <wagi@...om.org>
Cc: linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
blamoreaux@...are.com, frederic.martinsons@...il.com,
srivatsa@...il.mit.edu, vsirnapalli@...are.com,
amakhalov@...are.com, keerthanak@...are.com, ankitja@...are.com,
bordoloih@...are.com, srivatsab@...are.com,
Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH 4.19-rt] workqueue: Fix deadlock due to recursive locking
of pool->lock
On 2023-02-28 14:49:38 [-0800], 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().
Daniel, I double checked and this patch is correct - the backport was
faulty. Could you please pick it up and release an update?
Sebastian
Powered by blists - more mailing lists