From: Prateek Sood <prsood@codeaurora.org>
To: Boqun Feng <boqun.feng@gmail.com>, Peter Zijlstra <peterz@infradead.org>
Cc: tj@kernel.org, lizefan@huawei.com, cgroups@vger.kernel.org,
mingo@kernel.org, longman@redhat.com,
linux-kernel@vger.kernel.org, sramana@codeaurora.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] cgroup/cpuset: remove circular dependency deadlock
Date: Thu, 7 Sep 2017 14:37:15 +0530 [thread overview]
Message-ID: <88abfcfd-3d85-b903-e404-d101c34613a8@codeaurora.org> (raw)
In-Reply-To: <20170907085534.GA30135@tardis>
On 09/07/2017 02:26 PM, Boqun Feng wrote:
> On Thu, Sep 07, 2017 at 09:28:48AM +0200, Peter Zijlstra wrote:
>> On Thu, Sep 07, 2017 at 11:34:12AM +0530, 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 - percpu_down_write(&cpu_hotplug_lock) [held]
>>> flush(work) [no high prio workqueue available on CPU]
>>> wait_for_completion()
>
> Hi Prateek,
>
> so this is:
>
> _cpu_down():
> cpus_write_lock(); // percpu_down_write(&cpu_hotlug_lock)
> cpuhp_invoke_callbacks():
> workqueue_offine_cpu():
> wq_update_unbound_numa():
> alloc_unbound_pool():
> get_unbound_pool():
> create_worker():
> kthread_create_on_node():
> wake_up_process(kthreadd_task);
> wait_for_completion(); // create->done
>
> , right?
>
> Wonder running in a kworker is necessary to trigger this, I mean running
> a cpu_down() in a normal process context could also trigger this, no?
> Just ask out of curiosity.
>
> Regards,
> Boqun
Hi Boqun,
cpu_down() in normal process can also trigger this.
Regards
Prateek
>
>>>
>>> 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]
>>> percpu_down_read(&cpu_hotplug_lock) [waiting]
>>
>> That's both unreadable and useless :/ You want to tell what code paths
>> that were, not which random tasks happened to run them.
>>
>>
> [...]
>
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation
Center, Inc., is a member of Code Aurora Forum, a Linux Foundation
Collaborative Project
next prev parent reply other threads:[~2017-09-07 9:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 6:04 [PATCH] cgroup/cpuset: remove circular dependency deadlock Prateek Sood
2017-09-07 7:28 ` Peter Zijlstra
2017-09-07 8:56 ` Boqun Feng
2017-09-07 9:07 ` Prateek Sood [this message]
2017-09-07 9:05 ` Prateek Sood
-- strict thread matches above, loose matches on Subject: below --
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
2017-09-06 11:48 Prateek Sood
2017-09-06 12:56 ` Waiman Long
2017-09-06 14:23 ` 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=88abfcfd-3d85-b903-e404-d101c34613a8@codeaurora.org \
--to=prsood@codeaurora.org \
--cc=boqun.feng@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sramana@codeaurora.org \
--cc=tglx@linutronix.de \
--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