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
| ||
|
Date: Mon, 16 Aug 2010 12:44:00 -0700 (PDT) From: David Miller <davem@...emloft.net> To: rostedt@...dmis.org Cc: eric.dumazet@...il.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, kaber@...sh.net, mingo@...e.hu, peterz@...radead.org Subject: Re: [LOCKDEP BUG][2.6.36-rc1] xt_info_wrlock? From: Steven Rostedt <rostedt@...dmis.org> Date: Mon, 16 Aug 2010 13:55:01 -0400 > Please tell me what prevents an interrupt going off after we grab the > xt_info_wrlock(cpu) in get_counters(). He's only accessing the per-cpu counter locks of other cpus. The per-cpu lock is only locally accessed by a cpu in software interrupt context. That is why his transformation is legal. Lockdep simply hasn't been informed of this invariant and has to assume the worst. -- 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