From: Waiman Long <longman@redhat.com>
To: Prateek Sood <prsood@codeaurora.org>,
tj@kernel.org, lizefan@huawei.com, cgroups@vger.kernel.org,
mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, sramana@codeaurora.org
Subject: Re: [PATCH] cgroup/cpuset: remove circular dependency deadlock
Date: Wed, 6 Sep 2017 08:56:41 -0400 [thread overview]
Message-ID: <3992b0d5-947c-e343-5c07-8da43af5646d@redhat.com> (raw)
In-Reply-To: <1504698535-8187-1-git-send-email-prsood@codeaurora.org>
On 09/06/2017 07:48 AM, Prateek Sood wrote:
> Remove circular dependency deadlock in a scenario where hotplug of CPU is
> being done while there is updation in cgroup and cpuset triggered from
> userspace.
>
> Example scenario:
> kworker/0:0 => kthreadd => init:729 => init:1 => kworker/0:0
>
> kworker/0:0 - lock(cpuhotplug.mutex) [held]
> flush(work) [no high prio workqueue available on CPU]
> wait_for_completion()
>
> kthreadd - percpu_down_read(cgroup_threadgroup_rwsem) [waiting]
>
> init:729 - percpu_down_write(cgroup_threadgroup_rwsem) [held]
> lock(cpuset_mutex) [waiting]
>
> init:1 - lock(cpuset_mutex) [held]
> lock(cpuhotplug.mutex) [waiting]
>
> Eliminate this dependecy by reordering locking of cpuset_mutex
> and cpuhotplug.mutex in following order
> 1. Acquire cpuhotplug.mutex
> 2. Acquire cpuset_mutex
>
> Signed-off-by: Prateek Sood <prsood@codeaurora.org>
Is this patch for the latest upstream kernel or 4.4? There is no
cpuhotplug.mutex anymore in upstream kernel. It is a per-cpu rwsem
cpu_hotplug_lock.
Cheers,
Longman
next prev parent reply other threads:[~2017-09-06 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 11:48 Prateek Sood
2017-09-06 12:56 ` Waiman Long [this message]
2017-09-06 14:23 ` Prateek Sood
2017-09-07 6:04 Prateek Sood
2017-09-07 7:28 ` Peter Zijlstra
2017-09-07 8:56 ` Boqun Feng
2017-09-07 9:07 ` Prateek Sood
2017-09-07 9:05 ` Prateek Sood
2017-09-07 13:56 Prateek Sood
2017-09-07 17:45 ` Peter Zijlstra
2017-09-08 2:13 ` Prateek Sood
2017-09-07 17:51 ` Peter Zijlstra
2017-10-09 13:27 ` Prateek Sood
2017-10-11 9:48 ` Peter Zijlstra
2017-10-25 8:39 ` Prateek Sood
2017-10-25 9:30 ` Peter Zijlstra
2017-10-26 11:52 ` Prateek Sood
2017-10-26 14:05 ` Waiman Long
2017-10-27 8:03 ` Prateek Sood
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=3992b0d5-947c-e343-5c07-8da43af5646d@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=prsood@codeaurora.org \
--cc=sramana@codeaurora.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®