selftests/seccomp: Check ENOSYS under tracing (11eb004e) · Commits · 戴 / test

There should be no difference between -1 and other negative syscalls while tracing. Cc: Keno Fischer <keno@juliacomputing.com> Tested-by:

tools/testing/selftests/seccomp/seccomp_bpf.c

+20 −0

Original line number	Diff line number	Diff line
		@@ -1942,6 +1942,26 @@ FIXTURE_TEARDOWN(TRACE_syscall)
		teardown_trace_fixture(_metadata, self->tracer);
		}

		TEST(negative_ENOSYS)
		{
		/*
		* There should be no difference between an "internal" skip
		* and userspace asking for syscall "-1".
		*/
		errno = 0;
		EXPECT_EQ(-1, syscall(-1));
		EXPECT_EQ(errno, ENOSYS);
		/* And no difference for "still not valid but not -1". */
		errno = 0;
		EXPECT_EQ(-1, syscall(-101));
		EXPECT_EQ(errno, ENOSYS);
		}

		TEST_F(TRACE_syscall, negative_ENOSYS)
		{
		negative_ENOSYS(_metadata);
		}

		TEST_F(TRACE_syscall, syscall_allowed)
		{
		/* getppid works as expected (no changes). */