lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 20 Feb 2010 17:30:55 +0800 From: Américo Wang <xiyou.wangcong@...il.com> To: Johannes Berg <johannes@...solutions.net> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [2.6.33-rc5] Weird deadlock when shutting down On Thu, Feb 18, 2010 at 5:36 PM, Johannes Berg <johannes@...solutions.net> wrote: > On Fri, 2010-01-29 at 15:41 +1100, Benjamin Herrenschmidt wrote: >> Hi Ingo ! >> >> Johannes and I see this on our quad G5s... it -could- be similar to >> one reported a short while ago by Xiaotian Feng <xtfeng@...il.com> >> under the subject [2.6.33-rc4] sysfs lockdep warnings on cpu hotplug. >> >> Basically, the machine deadlocks right after printing the following >> when doing a shutdown: >> >> halt/4071 is trying to acquire lock: >> (s_active){++++.+}, at: [<c0000000001ef868>] >> .sysfs_addrm_finish+0x58/0xc0 >> >> but task is already holding lock: >> (&per_cpu(cpu_policy_rwsem, cpu)){+.+.+.}, at: [<c0000000004cd6ac>] >> .lock_policy_rwsem_write+0x84/0xf4 >> >> which lock already depends on the new lock. >> >> the existing dependency chain (in reverse order) is: > > This is still happening with -rc8. Any news? > Hey, johannes Not sure if you made some mistake here, the one you report here [1] is _not_ the same with this one reported by Benjamin. Please make sure what you are talking about here is the same one. Thanks. 1. http://lkml.org/lkml/2010/2/18/33 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists