[lkml]   [2009]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: RFC: disablenetwork facility. (v4)
    On Sun, Dec 27, 2009 at 05:36:48PM +0900, Tetsuo Handa wrote:

    > Application writers know better what syscalls the application will call than
    > application users.

    Aren't you forgetting about libc? Seriously, any interface along the
    lines of "pass a set of syscall numbers to kernel" is DOA:
    * syscall numbers are architecture-dependent
    * there are socketcall-style multiplexors (sys_ipc, anyone?)
    * libc is free to substitute one for another
    * libc is free to do so in arch-specific manner
    * libc is free to do so in kernel-revision-specific manner
    * libc is free to do so in libc-revision-specific manner
    (... and does all of the above)
    * new syscalls get added
    * e.g. on sparc64 32bit task can issue 64bit syscalls

     \ /
      Last update: 2009-12-27 09:53    [W:0.018 / U:21.392 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site