From: Thomas Gleixner <tglx@kernel.org>
To: Mark Brown <broonie@kernel.org>, Yuwen Chen <ywen.chen@foxmail.com>
Cc: akpm@linux-foundation.org, andrealmeid@igalia.com,
bigeasy@linutronix.de, colin.i.king@gmail.com, dave@stgolabs.net,
dvhart@infradead.org, edliaw@google.com, justinstitt@google.com,
kernel-team@android.com, licayy@foxmail.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
luto@mit.edu, mingo@redhat.com, morbo@google.com,
nathan@kernel.org, ndesaulniers@google.com, peterz@infradead.org,
shuah@kernel.org, usama.anjum@collabora.com, wakel@google.com,
mark.rutland@arm.com
Subject: Re: [PATCH v8 2/2] selftests/futex: fix the failed futex_requeue test issue
Date: Wed, 08 Jul 2026 01:31:45 +0200 [thread overview]
Message-ID: <87cxwys7fi.ffs@fw13> (raw)
In-Reply-To: <a8886f13-e6e4-4561-a2b1-db2bd3f77a6a@sirena.org.uk>
On Tue, Jul 07 2026 at 23:28, Mark Brown wrote:
> On Mon, May 18, 2026 at 10:16:54AM +0800, Yuwen Chen wrote:
>
> I'm seeing failures on arm64 (running a system with 4xA53) in -next in
> this test which bisect to this commit, the commit seems obviously
> plausible but I didn't actually investigate:
>
> # TAP version 13
> 1..2
> # Starting 2 tests from 1 test cases.
> # RUN global.requeue_single ...
> # futex_requeue.c:28:requeue_single:Expected res (-1) == 0 (0)
> # futex_requeue.c:29:requeue_single:waiter failed errno 110: Connection timed out
> # futex_requeue.c:49:requeue_single:Expected futex_wait_for_thread(&waiter, _metadata) (110) == 0 (0)
> # futex_requeue.c:50:requeue_single:Wait for thread failed
Do you have /proc/ disabled by chance or is it not accessible for the
test case?
> Full log should be at:
>
> https://lava.sirena.org.uk/scheduler/job/2954705#L13289
>
> but I'm having a terrible time with AI scrapers right now so perhaps not
> usefully.
Seems to correlate with the test case failure: Connection timed out :)
next prev parent reply other threads:[~2026-07-07 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 2:15 [PATCH v8 0/2] selftests/futex: fix the failed futex_requeue test issue Yuwen Chen
2026-05-18 2:16 ` [PATCH v8 1/2] selftests/futex: implement the interfaces related to threads Yuwen Chen
2026-07-05 19:54 ` [tip: locking/futex] selftests/futex: Provide thread creation and synchronization helpers tip-bot2 for Yuwen Chen
2026-05-18 2:16 ` [PATCH v8 2/2] selftests/futex: fix the failed futex_requeue test issue Yuwen Chen
2026-05-19 2:06 ` Yuwen Chen
2026-07-05 19:54 ` [tip: locking/futex] selftests/futex: Use thread synchronization helpers instead of usleep() tip-bot2 for Yuwen Chen
2026-07-07 22:28 ` [PATCH v8 2/2] selftests/futex: fix the failed futex_requeue test issue Mark Brown
2026-07-07 23:31 ` Thomas Gleixner [this message]
2026-07-07 23:48 ` Mark Brown
2026-07-08 1:54 ` Yuwen Chen
2026-07-08 8:08 ` Thomas Gleixner
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=87cxwys7fi.ffs@fw13 \
--to=tglx@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=broonie@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=edliaw@google.com \
--cc=justinstitt@google.com \
--cc=kernel-team@android.com \
--cc=licayy@foxmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mark.rutland@arm.com \
--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=usama.anjum@collabora.com \
--cc=wakel@google.com \
--cc=ywen.chen@foxmail.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