lkml.org 
[lkml]   [1999]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: access_ok inside kernelspace
Date
From
> calling sys_function() functions directly doesn't look right:
>
> 1. what if one was to do some accounting of the system calls. Not going
> through the int 0x80 would break this.

If you are accounting system calls then you don't wish to account internal
use of functions by the kernel. The app made _one_ syscall. You count it
once.

> 2. what if one were to temporarily redirect some system calls to another
> handler (like timetravel.o module does).

The internal calls are not syscalls. It makes total sense for the kernel to
use its own functions to implement things cleanly. Are you redirecting a
syscall or a function. The former you change the syscall table, the latter
you tweak the kernel to use a function pointer

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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