From: Yuwen Chen <ywen.chen@foxmail.com>
To: andrealmeid@igalia.com, akpm@linux-foundation.org
Cc: edliaw@google.com, dave@stgolabs.net, dbueso@suse.de,
dvhart@infradead.org, hpa@linux.intel.com,
justinstitt@google.com, kernel-team@android.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
llvm@lists.linux.dev, luto@mit.edu, mingo@redhat.com,
morbo@google.com, nathan@kernel.org, ndesaulniers@google.com,
peterz@infradead.org, shuah@kernel.org, tglx@linutronix.de,
usama.anjum@collabora.com
Subject: [PATCH 0/3] selftests/futex: fix the issue of abnormal test results caused by thread timing
Date: Thu, 11 Dec 2025 16:36:12 +0800 [thread overview]
Message-ID: <tencent_3739CFB7F300BEAEBB928A0EB8D1C6875C09@qq.com> (raw)
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/
next reply other threads:[~2025-12-11 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 8:36 Yuwen Chen [this message]
2025-12-11 8:38 ` [PATCH 1/3] selftests/futex: reduce array declarations in the requeue_single Yuwen Chen
2025-12-11 8:38 ` [PATCH 2/3] selftests/futex: use pthread_join to reclaim thread resources Yuwen Chen
2025-12-11 8:38 ` [PATCH 3/3] selftests/futex: fix the issue of abnormal test results caused by thread timing Yuwen Chen
2025-12-12 4:30 ` Licay
2025-12-15 7:50 ` Yuwen Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_3739CFB7F300BEAEBB928A0EB8D1C6875C09@qq.com \
--to=ywen.chen@foxmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=dvhart@infradead.org \
--cc=edliaw@google.com \
--cc=hpa@linux.intel.com \
--cc=justinstitt@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@mit.edu \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=usama.anjum@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®