Messages in this thread | | | Date | Sun, 29 May 2011 16:39:47 +0200 | From | Mikael Pettersson <> | Subject | Re: [GIT pull] x86 vdso updates |
| |
Ingo Molnar writes: > > * Andrew Lutomirski <luto@mit.edu> wrote: > > > On Fri, May 27, 2011 at 7:36 AM, Andrew Lutomirski <luto@mit.edu> wrote: > > > 3. Add int 0xcc and use it from vgettimeofday. It will SIGSEGV if > > > called from a user address (so it has no risk of ever becoming ABI) > > > and it will do gettimeofday if called from the right address. (I like ... > > Make it a real syscall but with extra constraints. It would have the > > same calling convention as the syscall instruction, but it would turn > > into SIGKILL if the calling address isn't in the VSYSCALL page
This will make things difficult for user-space dynamic binary instrumentation applications, since these normally execute generated code at different addresses than the original code.
Is there a safe fallback for this particular vsyscall?
/Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |