[lkml]   [2000]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] vsyscall feature
Ingo Molnar <> writes:
> yep - since kernel-entry-less vsyscalls are basically an extension to
> glibc, it's perfectly possible to avoid the intended behavior via
> user-space tricks. Just like it's possible currently to override the _time
> libc function. So anyone who wants to do tricks must either do it at the
> libc level if vsyscalls are use.

Depending on libc-level trickery alone is no good if complete control of a
(possibly rogue) user program is required. I think there still needs to be a
way (maybe a ptrace call?) to disable this.

> Also, since this is fully under the
> control of the kernel, it can be disabled (via a kernel recompile and/or
> kernel patch) without impacting any application.

I really hope the disable operation can go in the production kernel by
default. Won't it just be a few lines of code?

Any sufficiently adverse technology is indistinguishable from Microsoft.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.061 / U:2.364 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site