From: Hui Peng <benquike@gmail.com>
To: tglx@kernel.org, mingo@redhat.com, peterz@infradead.org,
dvhart@infradead.org, dave@stgolabs.net, andrealmeid@igalia.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] futex: fix hb lock mismatch in futex_wait_requeue_pi() and CLONE_VFORK hash init
Date: Sat, 19 Sep 2026 22:17:30 +0000 [thread overview]
Message-ID: <20260919221730.3707261-1-benquike@gmail.com> (raw)
Fix two issues in futex and fork initialization:
1. In futex_wait_requeue_pi(), if futex_wait_queue() returns with
q.lock_ptr updated tohb2's lock after a requeue timeout or signal
race, unlocking the original hb1 lock instead of q.lock_ptr leaves
hb2 locked and unlocks an unheld spinlock. Always unlock via
q.lock_ptr.
2. In copy_mm() (kernel/fork.c), initialize mm->futex_phash properly
when cloning so private futex hash state is consistent across
CLONE_VFORK.
Fixes: e5c6828493b5 ("futex: Split out requeue")
Assisted-by: LLM
Signed-off-by: Hui Peng <benquike@gmail.com>
---
diff --git a/kernel/fork.c b/kernel/fork.c
index a5934a317634..8f320f51cae8 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1996,9 +1996,9 @@ static bool need_futex_hash_allocate_default(u64 clone_flags)
{
/*
* Allocate a default futex hash for any sibling that will
- * share the parent's mm, except vfork.
+ * share the parent's mm.
*/
- return (clone_flags & (CLONE_VM | CLONE_VFORK)) == CLONE_VM;
+ return (clone_flags & CLONE_VM) != 0;
}
/*
diff --git a/kernel/futex/requeue.c b/kernel/futex/requeue.c
index b3f4a4bccb12..72b954d625c4 100644
--- a/kernel/futex/requeue.c
+++ b/kernel/futex/requeue.c
@@ -842,12 +842,13 @@ int futex_wait_requeue_pi(u32 __user *uaddr, unsigned int flags,
switch (futex_requeue_pi_wakeup_sync(&q)) {
case Q_REQUEUE_PI_IGNORE:
{
- CLASS(hbr, hbr)(&q.key);
- auto hb = hbr.hb;
+ struct futex_hash_bucket *hb;
+
/* The waiter is still on uaddr1 */
- spin_lock(&hb->lock);
+ futex_q_lockptr_lock(&q);
+ hb = container_of(q.lock_ptr, struct futex_hash_bucket, lock);
ret = handle_early_requeue_pi_wakeup(hb, &q, to);
- spin_unlock(&hb->lock);
+ spin_unlock(q.lock_ptr);
}
break;
next reply other threads:[~2026-09-19 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 22:17 Hui Peng [this message]
2026-09-21 22:43 ` André Almeida
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=20260919221730.3707261-1-benquike@gmail.com \
--to=benquike@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®