seccomp: Make syscall skipping and nr changes more consistent
authorAndy Lutomirski <luto@amacapital.net>
Mon, 1 Oct 2012 18:40:45 +0000 (11:40 -0700)
committerJames Morris <james.l.morris@oracle.com>
Tue, 2 Oct 2012 11:14:29 +0000 (21:14 +1000)
This fixes two issues that could cause incompatibility between
kernel versions:

 - If a tracer uses SECCOMP_RET_TRACE to select a syscall number
   higher than the largest known syscall, emulate the unknown
   vsyscall by returning -ENOSYS.  (This is unlikely to make a
   noticeable difference on x86-64 due to the way the system call
   entry works.)

 - On x86-64 with vsyscall=emulate, skipped vsyscalls were buggy.

This updates the documentation accordingly.

Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Acked-by: Will Drewry <wad@chromium.org>
Signed-off-by: James Morris <james.l.morris@oracle.com>

No differences found