]> git.ipfire.org Git - thirdparty/linux.git/commit
selftests/seccomp: Remove SIGSTOP si_pid check
authorKees Cook <keescook@chromium.org>
Thu, 6 Dec 2018 23:50:38 +0000 (15:50 -0800)
committerShuah Khan <shuah@kernel.org>
Wed, 12 Dec 2018 00:57:30 +0000 (17:57 -0700)
commit2bd61abead58c82714a1f6fa6beb0fd0df6a6d13
tree84bc6c5bc55599211c2b3b3aaf7bd0ce9113cd4e
parent651022382c7f8da46cb4872a545ee1da6d097d2a
selftests/seccomp: Remove SIGSTOP si_pid check

Commit f149b3155744 ("signal: Never allocate siginfo for SIGKILL or SIGSTOP")
means that the seccomp selftest cannot check si_pid under SIGSTOP anymore.
Since it's believed[1] there are no other userspace things depending on the
old behavior, this removes the behavioral check in the selftest, since it's
more a "extra" sanity check (which turns out, maybe, not to have been
useful to test).

[1] https://lkml.kernel.org/r/CAGXu5jJaZAOzP1qFz66tYrtbuywqb+UN2SOA1VLHpCCOiYvYeg@mail.gmail.com

Reported-by: Tycho Andersen <tycho@tycho.ws>
Suggested-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Shuah Khan <shuah@kernel.org>
tools/testing/selftests/seccomp/seccomp_bpf.c