From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754221Ab0DNANG (ORCPT ); Tue, 13 Apr 2010 20:13:06 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:51996 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752869Ab0DNANE (ORCPT ); Tue, 13 Apr 2010 20:13:04 -0400 Date: Tue, 13 Apr 2010 17:13:06 -0700 (PDT) Message-Id: <20100413.171306.25868761.davem@davemloft.net> To: fweisbec@gmail.com Cc: paulmck@linux.vnet.ibm.com, a.p.zijlstra@chello.nl, mingo@elte.hu, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Weird rcu lockdep warning From: David Miller In-Reply-To: <20100414000226.GH5602@nowhere> References: <20100413200432.GB5099@nowhere> <20100413234043.GG2538@linux.vnet.ibm.com> <20100414000226.GH5602@nowhere> X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Frederic Weisbecker 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.