[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100413.185106.46340154.davem@davemloft.net>
Date: Tue, 13 Apr 2010 18:51:06 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: paulmck@...ux.vnet.ibm.com
Cc: fweisbec@...il.com, a.p.zijlstra@...llo.nl, mingo@...e.hu,
sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Weird rcu lockdep warning
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Date: Tue, 13 Apr 2010 18:49:30 -0700
> On Tue, Apr 13, 2010 at 05:13:06PM -0700, David Miller wrote:
>> From: Frederic Weisbecker <fweisbec@...il.com>
>> Date: Wed, 14 Apr 2010 02:02:27 +0200
>>
>> > I just have a guess though....
>> > This seems to always happen from NMI path, and lockdep is disabled on NMI.
>> > I suspect the lock_acquire() performed by rcu_read_lock() is just ignored
>> > and then the rcu_read_lock_held() check has the wrong result...
>>
>> Yeah, I bet that's it too.
>>
>> lock_is_held() can't return anything meaningful while lockdep is
>> disabled, which it is during NMIs.
>
> Ah! So I just need to add a "current->lockdep_recursion"
> check to debug_lockdep_rcu_enabled(). And move the function to
> kernel/rcutree_plugin.h to avoid #include hell.
>
> See below for (untested) patch.
Looks good to me, Frederic please test :-)
--
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/
Powered by blists - more mailing lists