From: Suleiman Souhlal <suleiman@google.com>
To: linux-kernel@vger.kernel.org
Cc: "Suleiman Souhlal" <suleiman@google.com>,
"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>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
"Valentin Schneider" <vschneid@redhat.com>,
"K Prateek Nayak" <kprateek.nayak@amd.com>,
"zhidao su" <soolaugust@gmail.com>,
"John Stultz" <jstultz@google.com>,
"Qais Yousef" <qyousef@google.com>,
ssouhlal@FreeBSD.org
Subject: [RFC PATCH 06/12] futex: Address aborting from futex_lock_ping() while owning ping_state.
Date: Thu, 17 Sep 2026 04:33:30 +0000 [thread overview]
Message-ID: <20260917043339.2093426-7-suleiman@google.com> (raw)
In-Reply-To: <20260917043339.2093426-1-suleiman@google.com>
It is possible to unsuccesfully get out of the futex_lock_ping() loop
while owning the ping_state. This can happen when a waiting task gets
chosen by an unlocker as the top waiter, but gets a signal or its timeout
expires.
When this happens, wake up the next waiter and give them the ping_state.
Signed-off-by: Suleiman Souhlal <suleiman@google.com>
---
kernel/futex/ping.c | 72 ++++++++++++++++++++++++++++++++++++++-------
1 file changed, 61 insertions(+), 11 deletions(-)
diff --git a/kernel/futex/ping.c b/kernel/futex/ping.c
index 3d732489513b..ebcd3c4a7793 100644
--- a/kernel/futex/ping.c
+++ b/kernel/futex/ping.c
@@ -105,6 +105,43 @@ static void futex_unqueue_ping(struct futex_q *q)
q->ping_state = NULL;
}
+/*
+ * We own the ping_state but weren't able to get the futex.
+ * Wake up the next waiter and give them ownership.
+ */
+static void give_ping_state_to_next_waiter(struct futex_hash_bucket *hb,
+ union futex_key *key,
+ struct futex_pi_state *ping_state)
+{
+ struct futex_q *top_waiter;
+ DEFINE_WAKE_Q(wake_q);
+
+ raw_spin_lock_irq(&ping_state->ping_mutex.wait_lock);
+ /*
+ * Someone else got the futex and we don't need to do anything
+ * anymore, as it's their responsibility now.
+ */
+ if (ping_state->owner && ping_state->owner != current)
+ goto out;
+
+ top_waiter = futex_top_waiter(hb, key);
+ /*
+ * There are no other waiters but we leave the WAITERS bit set
+ * (with no owner or ping_state) to be cleaned up at a later unlock,
+ * at the cost of an extra syscall at the next lock operation, to
+ * keep things simple.
+ */
+ if (!top_waiter)
+ goto out;
+ get_ping_state(ping_state);
+ get_task_struct(top_waiter->task);
+ wake_q_add_safe(&wake_q, top_waiter->task);
+ ping_state_update_owner(ping_state, top_waiter->task);
+
+out:
+ raw_spin_unlock_irq_wake(&ping_state->ping_mutex.wait_lock, &wake_q);
+}
+
/* Returns >0 if lock acquired, <0 on error */
static int futex_trylock_ping_state(u32 __user *uaddr,
struct futex_pi_state *ping_state)
@@ -365,18 +402,31 @@ int futex_lock_ping(u32 __user *uaddr, unsigned int flags, ktime_t *time,
}
out_unqueue:
+ /*
+ * We got a pending signal or timeout, but the futex was handed
+ * off to us. Fix up the return value to indicate success.
+ */
+ if ((ret == -EINTR || ret == -ETIMEDOUT) &&
+ ping_mutex_owner(&q.ping_state->ping_mutex) == current)
+ ret = 0;
+
+ /*
+ * We are the pi_state owner but don't own the futex.
+ * This can happen if we get picked by the previous
+ * owner but get out without acquiring the lock for
+ * some reason.
+ * Wake up the next waiter and give the ping_state to them.
+ */
if (ret != 0 && q.ping_state->owner == current) {
- /*
- * We are pi_state owner but don't own the futex.
- * This can happen if we get picked by the previous
- * owner but get out without acquiring the lock for
- * some reason.
- * A later commit addresses this.
- */
- WARN_ON_ONCE(1);
- }
- /* This also puts the ping_state */
- futex_unqueue_ping(&q);
+ if (!plist_node_empty(&q.list))
+ __futex_unqueue(&q);
+ give_ping_state_to_next_waiter(hb, &q.key,
+ q.ping_state);
+ put_ping_state(q.ping_state);
+ } else
+ /* This also puts the ping_state */
+ futex_unqueue_ping(&q);
+
out_unlock:
futex_q_unlock(hb);
__release(q.lock_ptr);
--
2.55.0.1082.g2b9226bbc0-goog
next prev parent reply other threads:[~2026-09-17 4:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 4:33 [RFC PATCH 00/12] FUTEX_PING: A stealable futex using Proxy Execution Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 01/12] sched: Abstract task_struct->blocked_on by locking primitive Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 02/12] futex: Switch PI futex to use p->pi_futex_lock instead of p->pi_lock Suleiman Souhlal
2026-09-17 15:38 ` Peter Zijlstra
2026-09-18 7:11 ` Suleiman Souhlal
2026-09-18 10:07 ` K Prateek Nayak
2026-09-18 12:06 ` Peter Zijlstra
2026-09-17 4:33 ` [RFC PATCH 03/12] futex: Add "ping" parameter to pi_state management functions and export them Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 04/12] futex: Introduce stealable PI futex, FUTEX_*_PING Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 05/12] futex: Implement exit_ping_state_list() Suleiman Souhlal
2026-09-17 4:33 ` Suleiman Souhlal [this message]
2026-09-17 4:33 ` [RFC PATCH 07/12] futex: Make FUTEX_*_PING use Proxy Execution Suleiman Souhlal
2026-09-17 13:18 ` Jihan LIN
2026-09-17 14:39 ` K Prateek Nayak
2026-09-17 15:36 ` Peter Zijlstra
2026-09-17 4:33 ` [RFC PATCH 08/12] futex: Implement PING futex handoff Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 09/12] futex: Wake up donor in PING futex unlock Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 10/12] futex: Optimistic spinning for PING futexes Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 11/12] futex: Allow userspace stealing " Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 12/12] tools/testing/futex: Add ping_bench, a tool for benchmarking futexes Suleiman Souhlal
2026-09-17 8:58 ` [RFC PATCH 00/12] FUTEX_PING: A stealable futex using Proxy Execution Peter Zijlstra
2026-09-17 17:53 ` John Stultz
2026-09-17 18:51 ` Steven Rostedt
2026-09-18 6:30 ` Suleiman Souhlal
2026-09-18 8:25 ` Peter Zijlstra
2026-09-18 6:07 ` Suleiman Souhlal
2026-09-18 8:07 ` Peter Zijlstra
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=20260917043339.2093426-7-suleiman@google.com \
--to=suleiman@google.com \
--cc=andrealmeid@igalia.com \
--cc=bsegall@google.com \
--cc=dave@stgolabs.net \
--cc=dietmar.eggemann@arm.com \
--cc=dvhart@infradead.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qyousef@google.com \
--cc=rostedt@goodmis.org \
--cc=soolaugust@gmail.com \
--cc=ssouhlal@FreeBSD.org \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®