[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1261917194.5933.2.camel@penberg-laptop>
Date: Sun, 27 Dec 2009 14:33:14 +0200
From: Pekka Enberg <penberg@...helsinki.fi>
To: Andi Kleen <andi@...stfloor.org>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
paulmck@...ux.vnet.ibm.com, a.p.zijlstra@...llo.nl,
cl@...ux-foundation.org, Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: lockdep possible recursive lock in slab parent->list->rlock in
rc2
Hi Andi,
On Sun, 2009-12-27 at 13:06 +0100, Andi Kleen wrote:
> Get this on a NFS root system while booting
> This must be a recent change in the last week,
> I didn't see it in a post rc1 git* from last week
> (I haven't done a exact bisect)
>
> It's triggered by the r8169 driver close function,
> but looks more like a slab problem?
>
> I haven't checked it in detail if the locks are
> really different or just lockdep not knowing
> enough classes.
I broke the lockdep annotations in commit
ce79ddc8e2376a9a93c7d42daf89bfcbb9187e62 ("SLAB: Fix lockdep annotations
for CPU hotplug"). Does this fix things for you? Heiko, the following
patch should fix it for you too.
Pekka
diff --git a/mm/slab.c b/mm/slab.c
index 7d41f15..7451bda 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -654,7 +654,7 @@ static void init_node_lock_keys(int q)
l3 = s->cs_cachep->nodelists[q];
if (!l3 || OFF_SLAB(s->cs_cachep))
- return;
+ continue;
lockdep_set_class(&l3->list_lock, &on_slab_l3_key);
alc = l3->alien;
/*
@@ -665,7 +665,7 @@ static void init_node_lock_keys(int q)
* for alloc_alien_cache,
*/
if (!alc || (unsigned long)alc == BAD_ALIEN_MAGIC)
- return;
+ continue;
for_each_node(r) {
if (alc[r])
lockdep_set_class(&alc[r]->lock,
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists