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)
committerShuah Khan <shuahkh@osg.samsung.com>
Mon, 25 Sep 2017 16:09:05 +0000 (10:09 -0600)
commit10859f3855db4c6f10dc7974ff4b3a292f3de8e0
tree4156aa0d798033c0161608c3e6c598815b97ee66
parent659dbfd8c47adeb03f401d1a1f17091bb63cc5a2
selftests/seccomp: Support glibc 2.26 siginfo_t.h

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
Cc: stable@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>
tools/testing/selftests/seccomp/seccomp_bpf.c