lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <74d8f1bc-e2e0-4c14-b0b2-b1d9380a5b95@linuxfoundation.org>
Date: Wed, 19 Nov 2025 15:01:27 -0700
From: Shuah Khan <skhan@...uxfoundation.org>
To: Brendan Jackman <jackmanb@...gle.com>, Shuah Khan <shuah@...nel.org>
Cc: Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
 linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
 Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH RESEND v3] selftests/run_kselftest.sh: exit with error if
 tests fail

On 11/11/25 10:36, Brendan Jackman wrote:
> Parsing KTAP is quite an inconvenience, but most of the time the thing
> you really want to know is "did anything fail"?
> 
> Let's give the user the his information without them needing
> to parse anything.
> 
> Because of the use of subshells and namespaces, this needs to be
> communicated via a file. Just write arbitrary data into the file and
> treat non-empty content as a signal that something failed.
> 
> In case any user depends on the current behaviour, such as running this
> from a script with `set -e` and parsing the result for failures
> afterwards, add a flag they can set to get the old behaviour, namely
> --no-error-on-fail.
> 
> Signed-off-by: Brendan Jackman <jackmanb@...gle.com>

Applied to linux-kselftest next for Linux 6.19-rc1

thanks,
-- Shuah

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ