[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170611330425.2663547.18299563068150086794.b4-ty@chromium.org>
Date: Wed, 24 Jan 2024 08:21:47 -0800
From: Kees Cook <keescook@...omium.org>
To: luto@...capital.net,
wad@...omium.org,
shuah@...nel.org,
Terry Tritton <terry.tritton@...aro.org>
Cc: Kees Cook <keescook@...omium.org>,
linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org,
peter.griffin@...aro.org,
kernel-team@...roid.com,
bettyzhou@...gle.com
Subject: Re: [PATCH 0/3] selftests/seccomp seccomp_bpf test fixes
On Wed, 24 Jan 2024 14:13:54 +0000, Terry Tritton wrote:
> 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.
>
> [...]
Thanks for tracking all of these down. These look good to me.
Applied to for-next/seccomp, thanks!
[1/3] selftests/seccomp: Handle EINVAL on unshare(CLONE_NEWPID)
https://git.kernel.org/kees/c/18975ce05799
[2/3] selftests/seccomp: Change the syscall used in KILL_THREAD test
https://git.kernel.org/kees/c/fbcdf41167fe
[3/3] selftests/seccomp: user_notification_addfd check nextfd is available
https://git.kernel.org/kees/c/0c6f28a84431
Take care,
--
Kees Cook
Powered by blists - more mailing lists