[lkml]   [2000]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] vsyscall feature
Artur Skawina wrote:
> > is a downside to doing this. If, for example, timeofday is
> > available in a raw form on one of these data pages, and user-space
> > code can read that page at will (without going to the kernel), you
> > lose your ability to "lie" to user-space about the time.
> if you're saying absolutely everything must go through ptrace, even if
> it happens to have userspace-only implementation -- yes, obviously.
> preventing a rogue process from accessing the info directly might be a bit
> harder, w/o giving up the main benefit -- speed. There certainly seems to
> be a market for a runtime (global) on/off switch at least.

If you switch it off, the process knows you've switched it off and
may behave differently.

It's probably possible to lie to the process for gettimeofday and signal
operations though -- have the kernel unmap the page for those processes,
and have a ptrace SEGV handler which provides results as if the page
were still mapped.

-- Jamie

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.072 / U:1.544 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site