| 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
| ||
|
Message-Id: <20100413.171306.25868761.davem@davemloft.net> Date: Tue, 13 Apr 2010 17:13:06 -0700 (PDT) From: David Miller <davem@...emloft.net> To: fweisbec@...il.com Cc: paulmck@...ux.vnet.ibm.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: 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. -- 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