[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240124141357.1243457-1-terry.tritton@linaro.org>
Date: Wed, 24 Jan 2024 14:13:54 +0000
From: Terry Tritton <terry.tritton@...aro.org>
To: keescook@...omium.org,
	luto@...capital.net,
	wad@...omium.org,
	shuah@...nel.org
Cc: linux-kselftest@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	peter.griffin@...aro.org,
	kernel-team@...roid.com,
	bettyzhou@...gle.com,
	Terry Tritton <terry.tritton@...aro.org>
Subject: [PATCH 0/3] selftests/seccomp seccomp_bpf test fixes
Hi,
Here are a few fixes for seccomp_bpf tests found when testing on 
Android:
user_notification_sibling_pid_ns:
  unshare(CLONE_NEWPID) can return EINVAL so have added a check for this.
KILL_THREAD:
  This one is a bit more Android specific. 
  In Bionic pthread_create is calling prctl, this is causing the test to 
  fail as prctl is in the filter for this test and is killed when it is 
  called. I've just changed prctl to getpid in this case.
user_notification_addfd:
  This test can fail if there are existing file descriptors when the test 
  starts. It expects the next file descriptor to always increase 
  sequentially which is not always the case.
  Added a get_next_fd function to return the next expected file descriptor.
Regards,
Terry
Terry Tritton (3):
  selftests/seccomp: Handle EINVAL on unshare(CLONE_NEWPID)
  selftests/seccomp: Change the syscall used in KILL_THREAD test
  selftests/seccomp: user_notification_addfd check nextfd is available
 tools/testing/selftests/seccomp/seccomp_bpf.c | 41 ++++++++++++++-----
 1 file changed, 31 insertions(+), 10 deletions(-)
-- 
2.43.0.429.g432eaa2c6b-goog
Powered by blists - more mailing lists