linux-kernel - Re: 3.2-rc1: INFO: possible recursive locking detected

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]

Date:	Fri, 11 Nov 2011 07:48:45 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Yong Zhang <yong.zhang0@...il.com>, linux-kernel@...r.kernel.org,
	Pekka Enberg <penberg@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>, cl@...two.org
Subject: Re: 3.2-rc1: INFO: possible recursive locking detected

On Fri, Nov 11, 2011 at 08:43:13AM -0600, Christoph Lameter wrote:
> On Thu, 10 Nov 2011, Paul E. McKenney wrote:
> 
> > On Wed, Nov 09, 2011 at 05:05:57PM +0800, Yong Zhang wrote:
> > > Hi,
> > >
> > > Just get below waring when doing:
> > > for i in `seq 1 10`; do ./perf bench -f simple sched messaging -g 40; done
> > >
> > > And kernel config is attached.
> >
> > This appears to me to be the same false positive from the slab allocator
> > that has been seen before.  Christoph, any progress on this?
> 
> No this is another issue because it is not SLAB but SLUB. Must be a bug
> introduced by the recent merges of the per cpu partial list support.

Ah, OK.  Thank you for looking this over and for the suggested solutions!

							Thanx, Paul

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