linux-kernel - [PATCH 0/3] selftests/futex: fix the issue of abnormal test results caused by thread timing

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

Message-ID: <tencent_3739CFB7F300BEAEBB928A0EB8D1C6875C09@qq.com>
Date: Thu, 11 Dec 2025 16:36:12 +0800
From: Yuwen Chen <ywen.chen@...mail.com>
To: andrealmeid@...lia.com,
	akpm@...ux-foundation.org
Cc: edliaw@...gle.com,
	dave@...olabs.net,
	dbueso@...e.de,
	dvhart@...radead.org,
	hpa@...ux.intel.com,
	justinstitt@...gle.com,
	kernel-team@...roid.com,
	linux-kernel@...r.kernel.org,
	linux-kselftest@...r.kernel.org,
	llvm@...ts.linux.dev,
	luto@....edu,
	mingo@...hat.com,
	morbo@...gle.com,
	nathan@...nel.org,
	ndesaulniers@...gle.com,
	peterz@...radead.org,
	shuah@...nel.org,
	tglx@...utronix.de,
	usama.anjum@...labora.com
Subject: [PATCH 0/3] selftests/futex: fix the issue of abnormal test results caused by thread timing

On the Android arm32 platform, when performing the futex_requeue test, it will
most likely return a failure. The specific reason is detailed in a commit[1]
previously submitted by Edward Liaw. However, this commit cannot perfectly
solve the problem. This is because using a barrier does not guarantee that
the child thread will wait on futex_wait.

This series of patches attempts to solve this problem by checking whether
the child thread is in a sleeping state. This is because when the child thread
goes to sleep, it indicates that it is waiting for the futex lock.

Link: https://lore.kernel.org/all/20240918231102.234253-1-edliaw@google.com/