linux-kernel - Re: [PATCH] selftests: fuxex: Report a unique test name per run of futex_requeue

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] [thread-next>] [day] [month] [year] [list]

Date: Wed, 14 Feb 2024 13:08:31 -0800
From: Davidlohr Bueso <dave@...olabs.net>
To: Mark Brown <broonie@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Darren Hart <dvhart@...radead.org>,
	Andrï¿½ Almeida <andrealmeid@...lia.com>,
	Shuah Khan <shuah@...nel.org>, linux-kernel@...r.kernel.org,
	linux-kselftest@...r.kernel.org
Subject: Re: [PATCH] selftests: fuxex: Report a unique test name per run of
 futex_requeue_pi

On Tue, 13 Feb 2024, Mark Brown wrote:

>The futex_requeue_pi test program is run a number of times with different
>options to provide multiple test cases. Currently every time it runs it
>reports the result with a consistent string, meaning that automated systems
>parsing the TAP output from a test run have difficulty in distinguishing
>which test is which.
>
>The parameters used for the test are already logged as part of the test
>output, let's use the same format to roll them into the test name that we
>use with KTAP so that automated systems can follow the results of the
>individual cases that get run.
>
>Signed-off-by: Mark Brown <broonie@...nel.org>

Acked-by: Davidlohr Bueso <dave@...olabs.net>