|Prev Next||OpenBSD and Rthreads||Slide #32|
some platforms (powerpc) need to write two regions under same lock: __mwritev?
need to do proper ordering and cache syncs for the platforms
sparc: write back to front, doing isync instructions
maybe just a bad idea: won't this just be target for attackers?
kernel to check address of caller and only let ld.so call it?
probably doesn't help against return-oriented-programming
|EuroBSDCon 2012||Copyright © 2012 Philip Guenther|