From: David Howells <dhowells@redhat.com>
To: =?UTF-8?Q?Am=C3=A9rico_Wang?= <xiyou.wangcong@gmail.com>,
torvalds@osdl.org, akpm@linux-foundation.org
Cc: dhowells@redhat.com,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [2.6.33-rc5] Weird deadlock when shutting down
Date: Fri, 26 Mar 2010 12:22:02 +0000 [thread overview]
Message-ID: <6253.1269606122@redhat.com> (raw)
In-Reply-To: <2375c9f91003251943r4663ae51r5791acc374b6ccc4@mail.gmail.com>
Américo Wang <xiyou.wangcong@gmail.com> wrote:
> > =======================================================
> > [ INFO: possible circular locking dependency detected ]
> > 2.6.34-rc2-cachefs #115
> > -------------------------------------------------------
> > halt/2291 is trying to acquire lock:
> > (s_active#31){++++.+}, at: [<ffffffff81104950>] sysfs_addrm_finish+0x31/0x5a
> >
> > but task is already holding lock:
> > (&per_cpu(cpu_policy_rwsem, cpu)){+++++.}, at: [<ffffffff812a3a92>] lock_policy_rwsem_write+0x4a/0x7b
> >
> > which lock already depends on the new lock.
> >
>
>
> I already send a patch for this:
>
> https://patchwork.kernel.org/patch/83558/
>
> It is still in -mm tree, I think.
Tested-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2010-03-26 12:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 4:41 [2.6.33-rc5] Weird deadlock when shutting down Benjamin Herrenschmidt
2010-02-18 9:36 ` Johannes Berg
2010-02-18 16:31 ` Linus Torvalds
2010-02-18 18:45 ` Johannes Berg
2010-02-20 7:13 ` Américo Wang
2010-02-20 8:56 ` Johannes Berg
2010-02-20 9:06 ` Américo Wang
2010-02-20 10:53 ` Johannes Berg
2010-02-20 11:28 ` Johannes Berg
2010-02-20 12:07 ` Johannes Berg
2010-02-20 13:44 ` Américo Wang
2010-02-20 13:57 ` Johannes Berg
2010-02-21 9:51 ` Américo Wang
2010-02-21 10:17 ` Johannes Berg
2010-02-22 8:19 ` Américo Wang
2010-02-22 8:39 ` Johannes Berg
2010-02-21 10:43 ` Johannes Berg
2010-02-21 10:55 ` Xiaotian Feng
2010-02-21 11:12 ` Xiaotian Feng
2010-02-21 11:14 ` Johannes Berg
2010-02-21 11:22 ` Johannes Berg
2010-02-22 8:34 ` Américo Wang
2010-02-22 9:04 ` Johannes Berg
2010-02-22 9:12 ` Américo Wang
2010-02-22 9:14 ` Johannes Berg
2010-02-22 9:21 ` Américo Wang
2010-02-22 8:22 ` Américo Wang
2010-02-20 7:42 ` Dave Young
2010-02-20 8:46 ` Johannes Berg
2010-02-20 4:46 ` Américo Wang
2010-02-20 8:45 ` Johannes Berg
2010-02-20 9:30 ` Américo Wang
2010-02-20 10:52 ` Johannes Berg
2010-03-25 11:28 ` David Howells
2010-03-26 2:43 ` Américo Wang
2010-03-26 12:22 ` David Howells [this message]
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=6253.1269606122@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@osdl.org \
--cc=xiyou.wangcong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox