On Thu, Apr 12, 2012 at 2:48 PM, Will Drewry <wad@xxxxxxxxxxxx> wrote: > Enable support for seccomp filter on x86: > - syscall_get_arch() > - syscall_get_arguments() > - syscall_rollback() > - syscall_set_return_value() > - SIGSYS siginfo_t support > - secure_computing is called from a ptrace_event()-safe context > - secure_computing return value is checked (see below). > > SECCOMP_RET_TRACE and SECCOMP_RET_TRAP may result in seccomp needing to > skip a system call without killing the process. This is done by > returning a non-zero (-1) value from secure_computing. This change > makes x86 respect that return value. > > To ensure that minimal kernel code is exposed, a non-zero return value > results in an immediate return to user space (with an invalid syscall > number). > > Signed-off-by: Will Drewry <wad@xxxxxxxxxxxx> > Reviewed-by: H. Peter Anvin <hpa@xxxxxxxxx> > Acked-by: Eric Paris <eparis@xxxxxxxxxx> Reviewed-by: Kees Cook <keescook@xxxxxxxxxxxx> -- Kees Cook ChromeOS Security -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
