linux-kernel - Re: Linux 3.6-rc4

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: <20120921211639.GA17379@redhat.com>
Date:	Fri, 21 Sep 2012 17:16:39 -0400
From:	Dave Jones <davej@...hat.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Linux 3.6-rc4

On Mon, Sep 10, 2012 at 04:36:20PM +0200, Peter Zijlstra wrote:
 > On Fri, 2012-09-07 at 11:39 -0700, Linus Torvalds wrote:
 > > Al? Please look into this. I'm not entirely sure what's going on, but
 > > lockdep complains about this:
 > > 
 > >  Possible interrupt unsafe locking scenario:
 > > 
 > >        CPU0                    CPU1
 > >        ----                    ----
 > >   lock(&(&p->alloc_lock)->rlock);
 > >                                local_irq_disable();
 > >                                lock(&(&new_timer->it_lock)->rlock);
 > >                                lock(tasklist_lock);
 > >   <Interrupt>
 > >     lock(&(&new_timer->it_lock)->rlock);
 > > 
 > >  *** DEADLOCK ***
 > > 
 > > and it looks real. IOW, if I read that right, we have the task_lock ->
 > > it_lock dependency through exit_itimers(), and then we have the
 > > tasklist_lock -> task_lock dependency everywhere else. So now it_lock
 > > -> tasklist_lock becomes a deadlock. 
 > 
 > Agreed, I've got the following series from Oleg queued to solve this:
 > 
 >  http://marc.info/?l=linux-kernel&m=134600821828491&w=2

What's happening with this series ? I'm still seeing these traces in rc6.

	Dave

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