| 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: <a36005b50709161346t544d3927mfbca537c869c3c58@mail.gmail.com> Date: Sun, 16 Sep 2007 13:46:29 -0700 From: "Ulrich Drepper" <drepper@...il.com> To: "Francis Moreau" <francis.moro@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: x86_64: vsyscall vs vdso On 9/16/07, Francis Moreau <francis.moro@...il.com> wrote: > I'm a bit puzzled because vdso doesn't seem to be used on my fedora 7: > I just compiled a trivial program which just call gettimeofday() and > ld.so resolves this call with vsyscall's gettimeofday. > > Now I'm wondering when vdso is used, could anybody give me a clue ? F7 was released before the vdso for x86_64 was upstream so you should not expect anything else. F8 will use the available vdso. This doesn't just happen magically, changes to libc are needed. > Another question: is vdso going to replace vsyscall at all ? If so how > are statically programs going to be handled ? Unfortunately the vsyscalls cannot ever go completely away. Statically linked apps, the bane of progress, will need them. There are also people updating kernels but not the user userland code. What we will have to do in future is to make vsyscalls configurable. Both a compile time option and a runtime option (perhaps also under control of SELinux) are likely needed. - 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