linux-kernel - Re: [BUG] Lockdep recursive locking in kmem_cache

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, 28 Jul 2006 08:14:07 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Arjan van de Ven <arjan@...radead.org>,
	Christoph Lameter <clameter@....com>
Subject: Re: [BUG] Lockdep recursive locking in kmem_cache_free

On Fri, 2006-07-28 at 08:22 +0300, Pekka Enberg wrote:
> Hi Thomas,
> Looks bad.
> 
>   cache_reap
>   reap_alien	(grabs l3->alien[node]->lock)
>   __drain_alien_cache
>   free_block
>   slab_destroy	(slab management off slab)
>   kmem_cache_free
>   __cache_free
>   cache_free_alien (recursive attempt on l3->alien[node] lock)
> 
> Christoph?

If you need more info, I can add debugs. It happens every bootup.

	tglx


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