Kees Cook 2bd61abead selftests/seccomp: Remove SIGSTOP si_pid check ... Commit f149b31557 ("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>		2018-12-11 17:57:30 -07:00
..
.gitignore	selftests: seccomp: update .gitignore with newly added tests	2017-11-15 08:01:42 -07:00
config	selftests: create test-specific kconfig fragments	2016-02-25 09:47:52 -07:00
Makefile	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
seccomp_benchmark.c	selftests/seccomp: Add simple seccomp overhead benchmark	2017-08-14 13:46:41 -07:00
seccomp_bpf.c	selftests/seccomp: Remove SIGSTOP si_pid check	2018-12-11 17:57:30 -07:00