linux-kernel - Re: [2.6.33-rc1] slab: 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] [day] [month] [year] [list]

Message-ID: <20091218144533.GA19392@osiris.boeblingen.de.ibm.com>
Date:	Fri, 18 Dec 2009 15:45:33 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	paulmck@...ux.vnet.ibm.com, a.p.zijlstra@...llo.nl,
	cl@...ux-foundation.org
Subject: Re: [2.6.33-rc1] slab: possible recursive locking detected

On Fri, Dec 18, 2009 at 02:58:13PM +0200, Pekka Enberg wrote:
> Hi Heiko,
> 
> On Fri, 2009-12-18 at 12:58 +0100, Heiko Carstens wrote:
> > Just got this with CONFIG_SLAB:
> > 
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > 2.6.33-rc1-dirty #23
> > ---------------------------------------------
> > events/5/20 is trying to acquire lock:
> >  (&(&parent->list_lock)->rlock){..-...}, at: [<00000000000ee898>] cache_flusharray+0x3c/0x12c
> > 
> > but task is already holding lock:
> >  (&(&parent->list_lock)->rlock){..-...}, at: [<00000000000eee52>] drain_array+0x52/0x100
[...]
>
> Thanks for the report! Does reverting the following commit make the
> warning go away?
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ce79ddc8e2376a9a93c7d42daf89bfcbb9187e62

Yes, with that one reverted the warning is away.
--
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/