selftests/seccomp: Be more precise with syscall arguments.
authorRobert Sesek <rsesek@google.com>
Mon, 2 Nov 2015 20:28:49 +0000 (15:28 -0500)
committerShuah Khan <shuahkh@osg.samsung.com>
Mon, 2 Nov 2015 21:41:02 +0000 (14:41 -0700)
commitfd88d16c58c2ad689a68d6790c789e7d5be3fc5b
treec5428d64cb4c8942cac53694828bf261f9b76f08
parent256d0afb11d6e878e8c793e4a6e3bbfb81f9aae8
selftests/seccomp: Be more precise with syscall arguments.

Certain syscall emulation layers strictly check that the number of
arguments match what the syscall handler expects. The KILL_one_arg_one and
KILL_one_arg_six tests passed more parameters than expected to various
syscalls, causing failures in this emulation mode. Instead, test using
syscalls that take the appropriate number of arguments.

Signed-off-by: Robert Sesek <rsesek@google.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
tools/testing/selftests/seccomp/seccomp_bpf.c
This page took 0.024886 seconds and 5 git commands to generate.