Re: [RFC v1 04/17] selftest/seccomp: Fix the seccomp(2) signature
From: Kees Cook <hidden>
Date: 2016-03-24 04:36:41
Possibly related (same subject, not in this thread)
- 2016-03-24 · [RFC v1 04/17] selftest/seccomp: Fix the seccomp(2) signature · Mickaël Salaün <mic@digikod.net>
On Wed, Mar 23, 2016 at 6:46 PM, Mickaël Salaün [off-list ref] wrote:
Signed-off-by: Mickaël Salaün <redacted> Cc: Kees Cook <redacted> Cc: Andy Lutomirski <redacted> Cc: Will Drewry <redacted>
Another good catch. Shuah, can you take this one too? Acked-by: Kees Cook <redacted> -Kees
quoted hunk
--- tools/testing/selftests/seccomp/seccomp_bpf.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)diff --git a/tools/testing/selftests/seccomp/seccomp_bpf.c b/tools/testing/selftests/seccomp/seccomp_bpf.c index 9c1460f277c2..150829dd7998 100644 --- a/tools/testing/selftests/seccomp/seccomp_bpf.c +++ b/tools/testing/selftests/seccomp/seccomp_bpf.c@@ -1502,10 +1502,10 @@ TEST_F(TRACE_syscall, syscall_dropped) #endif #ifndef seccomp -int seccomp(unsigned int op, unsigned int flags, struct sock_fprog *filter) +int seccomp(unsigned int op, unsigned int flags, void *args) { errno = 0; - return syscall(__NR_seccomp, op, flags, filter); + return syscall(__NR_seccomp, op, flags, args); } #endif --2.8.0.rc3
-- Kees Cook Chrome OS & Brillo Security