linux-kernel - Re: [PATCH v2] selftests/seccomp: Pin benchmark to single CPU

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: <ZcJDjohKwXdWkABw@finisterre.sirena.org.uk>
Date: Tue, 6 Feb 2024 14:34:54 +0000
From: Mark Brown <broonie@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: kernel test robot <oliver.sang@...el.com>,
	Andy Lutomirski <luto@...capital.net>,
	Will Drewry <wad@...omium.org>, Shuah Khan <shuah@...nel.org>,
	linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
	linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2] selftests/seccomp: Pin benchmark to single CPU

On Tue, Feb 06, 2024 at 06:12:38AM -0800, Kees Cook wrote:
> The seccomp benchmark test (for validating the benefit of bitmaps) can
> be sensitive to scheduling speed, so pin the process to a single CPU,
> which appears to significantly improve reliability, and loosen the
> "close enough" checking to allow up to 10% variance instead of 1%.

Reviewed-by: Mark Brown <broonie@...nel.org>

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)