[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174681817502.2378444.17294454871668140127.b4-ty@kernel.org>
Date: Fri, 9 May 2025 12:16:18 -0700
From: Kees Cook <kees@...nel.org>
To: Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>,
Shuah Khan <shuah@...nel.org>,
Terry Tritton <terry.tritton@...aro.org>
Cc: Kees Cook <kees@...nel.org>,
linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] selftests/seccomp: fix negative_ENOSYS tracer tests on arm32
On Fri, 09 May 2025 12:56:22 +0100, Terry Tritton wrote:
> TRACE_syscall.ptrace.negative_ENOSYS and TRACE_syscall.seccomp.negative_ENOSYS
> on arm32 are being reported as failures instead of skipping.
>
> The teardown_trace_fixture function sets the test to KSFT_FAIL in case of a
> non 0 return value from the tracer process.
> Due to _metadata now being shared between the forked processes the tracer is
> returning the KSFT_SKIP value set by the tracee which is non 0.
>
> [...]
Ooh yes, nice catch!
Applied to for-next/seccomp, thanks!
[1/1] selftests/seccomp: fix negative_ENOSYS tracer tests on arm32
https://git.kernel.org/kees/c/73989c998814
Take care,
--
Kees Cook
Powered by blists - more mailing lists