[lkml]   [2002]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] remove sys_security
On Thu, Oct 17, 2002 at 10:20:21PM +0200, Russell Coker wrote:
> Now if every SE system call was to be a full Linux system call then LANANA
> would be involved in the discussions every time that a new SE call was added,
> which would not be desired by the SE Linux people or the LANANA people. So
> this means having a switch statement for the different SE calls.

Then stabilize your interface before going into production use. Why
should selinux (or lsm) get special treatment?

> Do we expect that SE Linux or other security system calls will be such a
> performance bottleneck that an extra switch or two will hurt?

It's not the performance issues, it's about getting a proper syscall table
instead of deep nesting without knowing what it actually does.
Look at e.g. the horrors of doing a proper 32->64bit translation
of those syscalls.

> Also it would mean that developmental projects would be more difficult.

Yes. In general you should avoid adding syscalls anyway. If we
wanted to make it easy we'd have created loadable syscalls from the very
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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