selftests/seccomp: Adjust test fixture counts
authorKees Cook <keescook@chromium.org>
Wed, 11 Mar 2020 19:21:28 +0000 (12:21 -0700)
committerShuah Khan <skhan@linuxfoundation.org>
Fri, 13 Mar 2020 19:32:04 +0000 (13:32 -0600)
The seccomp selftest reported the wrong test counts since it was using
slightly the wrong API for defining text fixtures. Adjust the API usage.

Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
tools/testing/selftests/seccomp/seccomp_bpf.c

index ee1b727ede045dfd920bf319d3729efd217ef137..7bf82fb07f67f616d952b893fa6ca0f5736ec73b 100644 (file)
@@ -909,7 +909,7 @@ TEST(ERRNO_order)
        EXPECT_EQ(12, errno);
 }
 
-FIXTURE_DATA(TRAP) {
+FIXTURE(TRAP) {
        struct sock_fprog prog;
 };
 
@@ -1020,7 +1020,7 @@ TEST_F(TRAP, handler)
        EXPECT_NE(0, (unsigned long)sigsys->_call_addr);
 }
 
-FIXTURE_DATA(precedence) {
+FIXTURE(precedence) {
        struct sock_fprog allow;
        struct sock_fprog log;
        struct sock_fprog trace;
@@ -1509,7 +1509,7 @@ void tracer_poke(struct __test_metadata *_metadata, pid_t tracee, int status,
        EXPECT_EQ(0, ret);
 }
 
-FIXTURE_DATA(TRACE_poke) {
+FIXTURE(TRACE_poke) {
        struct sock_fprog prog;
        pid_t tracer;
        long poked;
@@ -1817,7 +1817,7 @@ void tracer_ptrace(struct __test_metadata *_metadata, pid_t tracee,
                change_syscall(_metadata, tracee, -1, -ESRCH);
 }
 
-FIXTURE_DATA(TRACE_syscall) {
+FIXTURE(TRACE_syscall) {
        struct sock_fprog prog;
        pid_t tracer, mytid, mypid, parent;
 };
@@ -2321,7 +2321,7 @@ struct tsync_sibling {
                }                                                       \
        } while (0)
 
-FIXTURE_DATA(TSYNC) {
+FIXTURE(TSYNC) {
        struct sock_fprog root_prog, apply_prog;
        struct tsync_sibling sibling[TSYNC_SIBLINGS];
        sem_t started;