Re: [PATCH v8 2/2] selftests/futex: fix the failed futex_requeue test issue

[Thomas Gleixner]

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 :)