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: <20250527124327.5UDnm-ho@linutronix.de>
Date: Tue, 27 May 2025 14:43:27 +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 13:35:50 [+0100], Mark Brown wrote:
> On Tue, May 27, 2025 at 02:23:32PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2025-05-27 12:28:00 [+0100], Mark Brown wrote:
> 
> > > 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
> 
> > 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.
> 
> Yeah, I was a bit confused as well.  This is running with an installed
> copy of the selftests and IIRC the build is out of tree so it's possible
> something is different with that path compared to what you're doing?
> It's a common source of problems?

It shouldn't be. The test is self-contained and as long as the run.sh
script invokes all is good.  I don't see what futex_priv_hash might be
is doing different compared to the previous test.

I just noticed that after the two futex_priv_hash invocations there
should be one futex_numa_mpol invocation. That one is missing in the
output. Any idea why?

Sebastian