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, 12 Apr 2010 22:30:42 +0200 From: Arnd Bergmann <arnd@...db.de> To: Josh Triplett <josh@...htriplett.org> Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Eric Dumazet <eric.dumazet@...il.com>, David Howells <dhowells@...hat.com>, linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com, dipankar@...ibm.com, akpm@...ux-foundation.org, mathieu.desnoyers@...ymtl.ca, dvhltc@...ibm.com, niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu Subject: Re: [PATCH tip/core/urgent 1/4] rcu: add rcu_access_pointer and rcu_dereference_protected On Monday 12 April 2010 21:24:42 Josh Triplett wrote: > If you want to prevent people from deferencing the pointer directly, or > from assigning it to some other pointer, you could use Sparse's > __attribute__((noderef)) and > __attribute__((address_space(...)). > > See the definitions of __user and __iomem in include/linux/compiler.h > for instance. (And, looking at that file, now __percpu. Nice!) > > You'd then have to explicitly use __force at the point where you > legitimately dereference it. I have started a patch set for doing that a few weeks ago, still need to pick up that work again. Are there any other patches besides this series that I should base on top of now? Arnd -- 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