From: Max Krasnyansky <maxk@qualcomm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
Paul Menage <menage@google.com>,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Paul Jackson <pj@sgi.com>
Subject: Re: v2.6.26-rc7/cgroups: circular locking dependency
Date: Mon, 23 Jun 2008 23:29:21 -0700 [thread overview]
Message-ID: <48609441.2030901@qualcomm.com> (raw)
In-Reply-To: <1214149823.3223.313.camel@lappy.programming.kicks-ass.net>
Peter Zijlstra wrote:
> On Mon, 2008-06-23 at 00:34 +0900, KOSAKI Motohiro wrote:
>> CC'ed Paul Jackson
>>
>> it seems typical ABBA deadlock.
>> I think cpuset use cgrou_lock() by mistake.
>>
>> IMHO, cpuset_handle_cpuhp() sholdn't use cgroup_lock() and
>> shouldn't call rebuild_sched_domains().
>
> Looks like Max forgot to test with lockdep enabled...
Hmm, I don't think I actually changed any lock nesting/dependencies. Did I ?
Oh, I see rebuild_sched_domains() is now called from cpuset hotplug handler.
I just looked at the comment for rebuild_sched_domains() and it says
" * Call with cgroup_mutex held. ..." that's why I thought it's safe and it
worked on the test stations.
Anyway, we need definitely need to make rebuild_sched_domains() work from the
hotplug handler.
> Well, someone should when you change the online map.
>
> Max, Paul, can we handle this in update_sched_domains() instead?
That'd be exactly the same as calling rebuild_sched_domains() outside of the
cgroup_lock(). So I do not think it'll help. Paul has more info in his reply
so I'll reply to his email.
Max
next prev parent reply other threads:[~2008-06-24 6:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 17:38 v2.6.26-rc7/cgroups: circular locking dependency Vegard Nossum
2008-06-22 9:10 ` Cyrill Gorcunov
2008-06-22 9:42 ` Vegard Nossum
2008-06-22 9:42 ` Vegard Nossum
[not found] ` <19f34abd0806220242p62b9a044la6dd8843e5055f84-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-22 9:50 ` Cyrill Gorcunov
2008-06-22 9:50 ` Cyrill Gorcunov
2008-06-22 15:34 ` KOSAKI Motohiro
2008-06-22 15:50 ` Peter Zijlstra
2008-06-23 12:02 ` Paul Jackson
[not found] ` <1214149823.3223.313.camel-N9Ixq/CQ5vKdTX5a5knrm8zTDFooKrT+cvkQGrU6aU0@public.gmane.org>
2008-06-23 12:02 ` Paul Jackson
2008-06-24 6:29 ` Max Krasnyansky
2008-06-24 6:29 ` Max Krasnyansky [this message]
[not found] ` <48609441.2030901-zC7DfRvBq/JWk0Htik3J/w@public.gmane.org>
2008-06-26 7:25 ` Paul Menage
2008-06-26 7:25 ` Paul Menage
[not found] ` <6599ad830806260025u27458a47j47175ad778ca48a9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-26 17:45 ` Max Krasnyansky
2008-06-26 17:45 ` Max Krasnyansky
[not found] ` <2f11576a0806220834m3572ee80i72229cb9a1613558-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-22 15:50 ` Peter Zijlstra
2008-06-22 16:02 ` Cyrill Gorcunov
2008-06-22 16:02 ` Cyrill Gorcunov
[not found] ` <20080621173859.GA6846-nxaqs94rzLmmVpTN6tjYhgHPHiC6WJ74@public.gmane.org>
2008-06-22 9:10 ` Cyrill Gorcunov
2008-06-22 15:34 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2008-06-21 17:38 Vegard Nossum
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=48609441.2030901@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=containers@lists.linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=vegard.nossum@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.