linux-kernel - Re: Bisected rcu hang (kernel/sched.c): was 2.6.33rc4 RCU hang mm spin_lock deadlock(?) after running libvirtd

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1264317584.6446.9.camel@marge.simson.net>
Date:	Sun, 24 Jan 2010 08:19:44 +0100
From:	Mike Galbraith <efault@....de>
To:	Michael Breuer <mbreuer@...jas.com>
Cc:	paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: Bisected rcu hang (kernel/sched.c): was 2.6.33rc4 RCU hang mm
 spin_lock deadlock(?) after running libvirtd - reproducible.

On Sun, 2010-01-24 at 01:32 -0500, Michael Breuer wrote:

> That commit solves my crash. Was my first time bisecting... thought I 
> got it right. With the referenced commit, the system crashed when 
> libvirtd was started, at the previous commit, it didn't crash. 
> Regardless, the commit in tip fixes the issue. Hopefully it'll solve 
> some of the other reported RCU hangs as well. Looks like the change for 
> freshly cloned tasks is key.

Great, and yeah, the freshly cloned bit is the fix for your scenario.

	-Mike

--
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/