syscall

Linux gives each process a 32 bit random seed, which is probably more useful (as is making a syscall).

There is a lot more historical baroque stuff about x86, like int 80, syscall, or sysenter?

Is anyone aware of an interface to seccomp-bpf on Linux that is as easy to use as this tame() syscall?

If you want to learn the syscall ABI on Linux you need to look at <asm/unistd.h>.

Docker (and my own Sandstorm.io) relies very heavily on Linux's syscall ABI compatibility promises.

Then, there is the question of what does Unicorn Engine do at user-level with instructions like syscall on x86_64 or sc in ppc64.

Third party libraries cause headaches too because their syscall footprint might conflict (now or in the future!) with the main program's seccomp configuration.

The C library specifies the index into this table when making a syscall.

Everything you can do with Linux, you can do through it's syscall interface.

IMO if you cannot directly do a syscall in an os its useless.

So unless you're hacking on the guts of the Linux syscall layer...

It's not an attack vector this syscall is meant to prevent.