linux-kernel - Re: lockdep recursive locking detected (rcu_kthread / __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]

Message-ID: <alpine.DEB.2.00.1110040948230.8522@router.home>
Date:	Tue, 4 Oct 2011 09:50:25 -0500 (CDT)
From:	Christoph Lameter <cl@...two.org>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Sitsofe Wheeler <sitsofe@...oo.com>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	penberg@...nel.org, mpm@...enic.com, linux-mm@...ck.org,
	David Rientjes <rientjes@...gle.com>
Subject: Re: lockdep recursive locking detected (rcu_kthread /
 __cache_free)

On Tue, 4 Oct 2011, Peter Zijlstra wrote:

> It could of course be I got confused and broke stuff instead, could
> someone who knows slab (I guess that's either Pekka, Christoph or David)
> stare at those patches?

Why is the loop in init_lock_keys only running over kmalloc caches and not
over all slab caches? It seems that this has to be especially applied to
regular slab caches because those are the ones that mostly have off slab
structures. So modify init_lock_keys to run over all slab caches?


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