From: Michal Pluta <michalpl2003@gmail.com>
To: acme@kernel.org, namhyung@kernel.org
Cc: "Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"James Clark" <james.clark@linaro.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH 0/8] perf bench futex: Fix several bugs and bad inputs
Date: Sat, 26 Sep 2026 20:03:59 +0100 [thread overview]
Message-ID: <20260926190407.1106421-1-michalpl2003@gmail.com> (raw)
This series fixes several bugs in the futex benchmarks of 'perf bench'.
I found them by running the benchmarks and reading the code, and then
trying edge-case inputs. They include hangs, wrong timing and throughput
numbers, and inputs that were silently ignored.
I used an LLM to check whether what I suspected were actually bugs, and
later to look for more edge cases. I reproduced and reviewed each one
myself.
This is my first patch submission, so I am happy to reword, reorder or
split any of the patches.
How I checked each problem, before the patch:
1. futex_wait() never returns EINTR, so the signal check never worked.
I confirmed the hang by sending SIGINT to one worker thread with
tgkill(2) while 'perf bench futex wake -t 8' was waiting: it hung.
2. 'perf bench futex wake -b 128' fails with an error from
futex_print_nbuckets().
3. Run 'perf bench futex hash -t 2 -r 30 -s' and send it SIGINT after
about 3 s: the throughput is much higher than in a full '-r 3' run.
The timing problem in the other benchmarks I confirmed by making
gettimeofday() advance by 1.5 s per call with an LD_PRELOAD shim.
4. 'perf bench futex requeue -q 0' and 'perf bench futex hash -f 0'
hang, and 'perf bench futex wake -b -128' silently ignores the -b.
5. I confirmed the hang by making FUTEX_WAKE fail with an LD_PRELOAD
shim.
6. Only affects 32-bit builds, see below.
I can share the small test programs for items 1, 3 and 5 if they are
useful.
Not tested:
- Patch 6 (64-bit counter) was built and run only on x86-64, as I have
no 32-bit setup.
- Patch 5 was tested with an injected failure, not with a real failing
system call.
- Everything else was run on x86-64 with a 7.0 kernel.
Patches 7 and 8 are optional cleanups.
The series is based on perf-tools-next, commit 528b1475f9cf ("perf mem
record: Use the IBS swfilt filter when available").
Thank you!
Michal Pluta (8):
perf bench futex: Retry futex_wait() when interrupted by a signal
perf bench futex: Set the number of hash buckets in futex wake
perf bench futex: Use the whole timeval for elapsed times
perf bench futex: Reject invalid -q, -f and -b values
perf bench futex: Stop when futex_wake() fails in futex wake
perf bench futex: Use a 64-bit operation counter in hash and lock-pi
perf bench futex: Clean up two nits in futex hash
perf bench futex: Fix wording in futex bench messages
tools/perf/bench/futex-hash.c | 23 +++++++++++++-------
tools/perf/bench/futex-lock-pi.c | 16 ++++++++------
tools/perf/bench/futex-requeue.c | 12 ++++++++---
tools/perf/bench/futex-wake-parallel.c | 15 +++++++------
tools/perf/bench/futex-wake.c | 30 ++++++++++++++++----------
tools/perf/bench/futex.c | 9 +++++---
6 files changed, 68 insertions(+), 37 deletions(-)
base-commit: 528b1475f9cffbaffb37f490e86780662471ef3f
--
2.43.0
next reply other threads:[~2026-09-26 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 19:03 Michal Pluta [this message]
2026-09-26 19:04 ` [PATCH 1/8] perf bench futex: Retry futex_wait() when interrupted by a signal Michal Pluta
2026-09-26 19:04 ` [PATCH 2/8] perf bench futex: Set the number of hash buckets in futex wake Michal Pluta
2026-09-26 19:04 ` [PATCH 3/8] perf bench futex: Use the whole timeval for elapsed times Michal Pluta
2026-09-26 19:04 ` [PATCH 4/8] perf bench futex: Reject invalid -q, -f and -b values Michal Pluta
2026-09-26 19:04 ` [PATCH 5/8] perf bench futex: Stop when futex_wake() fails in futex wake Michal Pluta
2026-09-26 19:04 ` [PATCH 6/8] perf bench futex: Use a 64-bit operation counter in hash and lock-pi Michal Pluta
2026-09-26 19:04 ` [PATCH 7/8] perf bench futex: Clean up two nits in futex hash Michal Pluta
2026-09-26 19:04 ` [PATCH 8/8] perf bench futex: Fix wording in futex bench messages Michal Pluta
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=20260926190407.1106421-1-michalpl2003@gmail.com \
--to=michalpl2003@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
/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®