Re: [patch] let CONFIG_SECCOMP default to n

Andi Kleen
2006-07-12T15:44:10Z

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> I really don't care about cpushare and patents for some users of the
> code in question. On the other hand turning on performance harming code
> for a tiny number of users is dumb. If it were a loadable module it
> would be different.

Actually there are some promising applications of seccomp outside
cpushare.

e.g. Andrea at some point proposed to run codecs which often
have security issues in a simple cpusec jail. That's ok for
them because they normally don't need to do any system calls.

I liked the idea. While this can be done with LSM (e.g. apparmor) too
seccomp is definitely much easier and simpler and more "obviously safe"
than anything LSM based.

If the TSC disabling code is taken out the runtime overhead
of seccomp is also very small because it's only tested in slow
paths.

-Andi