| 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: <20090719072210.GA3981@basil.fritz.box> Date: Sun, 19 Jul 2009 09:22:10 +0200 From: Andi Kleen <andi@...stfloor.org> To: john stultz <johnstul@...ibm.com> Cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...x.de>, lkml <linux-kernel@...r.kernel.org> Subject: Re: Duplicate vsyscall/vdso gettimeofday implementations on x86_64 > Ok. Ulrich mailed me with the same points earlier and here's what I > said: Hopefully he can fix the terrible vsyscall code in glibc too. > 1) Keep the old vsyscall gtod implementation as is, despite it > duplicating things. Maybe avoid the code duplication via inlined > functions. > > 2) Set the old vsyscall gtod to directly call the syscall. There were some more like 3) Call from old vsyscall into new vDSO code. This needs to store the randomized mapping address somewhere though. Most options required a another page for each process. And a couple of other variants. > Neither of these help to avoid the non-randomized syscall instruction. They used to be patched away to nops when not needed, unfortunately that code was removed at some point. Perhaps that should be readded. Most systems actually don't need them (only those that need pmtimer) so you don't have a static syscall entry point on them. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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