Dmitry V. Levin
e8a8f6d6e8
If kernel implementation of strict seccomp mode is buggy, test programs
will be killed by SIGKILL. This is a known problem at least on
x32 and mips. Skip affected tests if this is the case.
This change partially revert commit 9c1a72cd3f.
* tests/seccomp-strict.c (main): Remove workaround for x32.
* tests/prctl-seccomp-strict.c: Likewise.
* tests/seccomp-strict.test: Skip the test if the test program
has been killed by SIGKILL.
* tests/prctl-seccomp-strict.test: Likewise.
18 lines
360 B
Bash
Executable File
18 lines
360 B
Bash
Executable File
#!/bin/sh
|
|
|
|
# Check how seccomp SECCOMP_SET_MODE_STRICT is decoded.
|
|
|
|
. "${srcdir=.}/init.sh"
|
|
|
|
set -- "./$NAME"
|
|
"$@" > /dev/null || {
|
|
case $? in
|
|
77) skip_ "$* exited with code 77" ;;
|
|
137) framework_skip_ "$* killed by SIGKILL, fix your kernel" ;;
|
|
*) fail_ "$args failed" ;;
|
|
esac
|
|
}
|
|
run_strace -eseccomp "$@" > "$EXP"
|
|
match_diff "$LOG" "$EXP"
|
|
rm -f "$EXP"
|