linux-kernel - Re: [PATCH v12 20/21] selftests/futex: Add futex_priv

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]

Message-ID: <20250527122332.M0ucxhwh@linutronix.de>
Date: Tue, 27 May 2025 14:23:32 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Mark Brown <broonie@...nel.org>
Cc: linux-kernel@...r.kernel.org,
	André Almeida <andrealmeid@...lia.com>,
	Darren Hart <dvhart@...radead.org>,
	Davidlohr Bueso <dave@...olabs.net>, Ingo Molnar <mingo@...hat.com>,
	Juri Lelli <juri.lelli@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Valentin Schneider <vschneid@...hat.com>,
	Waiman Long <longman@...hat.com>
Subject: Re: [PATCH v12 20/21] selftests/futex: Add futex_priv_hash

On 2025-05-27 12:28:00 [+0100], Mark Brown wrote:
> On Wed, Apr 16, 2025 at 06:29:20PM +0200, Sebastian Andrzej Siewior wrote:
> > Test the basic functionality of the private hash:
> > - Upon start, with no threads there is no private hash.
> > - The first thread initializes the private hash.
> > - More than four threads will increase the size of the private hash if
> >   the system has more than 16 CPUs online.
> 
> This newly added test is not running successfully on arm64, it looks
> like it's just a straightforward integration issue:
> 
> # Usage: futex_priv_hash
> #   -c    Use color
> #   -g    Test global hash instead intead local immutable 
> #   -h    Display this help message
> #   -v L  Verbosity level: 0=QUIET 1=CRITICAL 2=INFO
> # Usage: futex_priv_hash
> #   -c    Use color
> #   -g    Test global hash instead intead local immutable 
> #   -h    Display this help message
> #   -v L  Verbosity level: 0=QUIET 1=CRITICAL 2=INFO
> not ok 1 selftests: futex: run.sh # exit=1

That is odd. If I run ./run.sh then it passes. I tried it with forcing
COLOR=-c and without it. This is the only option that is passed. That is on
x86 however but I doubt arm64 is doing anything special here.

A bit puzzled here.

> Full log:
> 
>    https://lava.sirena.org.uk/scheduler/job/1414260#L9910

Sebastian