linux-kernel - Re: [PATCH] kselftest/arm64: Ensure stable names for GCS stress test results

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: <172909620948.3163505.7404760502678129111.b4-ty@arm.com>
Date: Wed, 16 Oct 2024 17:30:16 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Will Deacon <will@...nel.org>,
	Shuah Khan <shuah@...nel.org>,
	Mark Brown <broonie@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org,
	linux-kselftest@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kselftest/arm64: Ensure stable names for GCS stress test results

On Fri, 11 Oct 2024 15:36:25 +0100, Mark Brown wrote:
> The GCS stress test program currently uses the PID of the threads it
> creates in the test names it reports, resulting in unstable test names
> between runs. Fix this by using a thread number instead.
> 
> 

Applied to arm64 (for-next/gcs), thanks!

[1/1] kselftest/arm64: Ensure stable names for GCS stress test results
      https://git.kernel.org/arm64/c/9b9be7825851

-- 
Catalin