selftests/seccomp: Support glibc 2.26 siginfo_t.h
authorKees Cook <keescook@chromium.org>
Thu, 7 Sep 2017 23:32:46 +0000 (16:32 -0700)
committerpopcornmix <popcornmix@gmail.com>
Fri, 6 Oct 2017 12:06:50 +0000 (13:06 +0100)
commit8a799ec877d5a5a56d69f4f049e5391e50c4f174
treea65c8931d10bed4160e04c8b7127cf047794d60b
parenta4d8eacccc7a20cbfb1d80a20a5657179a4c2c6f
selftests/seccomp: Support glibc 2.26 siginfo_t.h

commit 10859f3855db4c6f10dc7974ff4b3a292f3de8e0 upstream.

The 2.26 release of glibc changed how siginfo_t is defined, and the earlier
work-around to using the kernel definition are no longer needed. The old
way needs to stay around for a while, though.

Reported-by: Seth Forshee <seth.forshee@canonical.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Will Drewry <wad@chromium.org>
Cc: Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Seth Forshee <seth.forshee@canonical.com>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
tools/testing/selftests/seccomp/seccomp_bpf.c