From: Davidlohr Bueso <dave@stgolabs.net>
To: tglx@kernel.org, peterz@infradead.org, mingo@redhat.com
Cc: keenanat2000@gmail.com, linux-kernel@vger.kernel.org,
syzbot+78147abe6c524f183ee9@syzkaller.appspotmail.com
Subject: Re: [PATCH -tip] locking/rtmutex: Skip remove_waiter() when waiter is not enqueued
Date: Wed, 3 Jun 2026 07:03:54 -0700 [thread overview]
Message-ID: <20260603140354.pluitgpliv6fl6fi@offworld> (raw)
In-Reply-To: <20260507112913.1019537-1-dave@stgolabs.net>
ping
On Thu, 07 May 2026, Davidlohr Bueso wrote:
>syzbot triggered the following splat in remove_waiter() via
>FUTEX_CMP_REQUEUE_PI:
>
> KASAN: null-ptr-deref in range [0x0000000000000a88-0x0000000000000a8f]
> class_raw_spinlock_constructor
> remove_waiter+0x159/0x1200 kernel/locking/rtmutex.c:1561
> rt_mutex_start_proxy_lock+0x103/0x120
> futex_requeue+0x10e4/0x20d0
> __x64_sys_futex+0x34f/0x4d0
>
>task_blocks_on_rt_mutex() does not arm the waiter upon deadlock detection,
>leaving waiter->task nil, where 3bfdc63936dd ("rtmutex: Use waiter::task instead
>of current in remove_waiter()") made this fatal.
>
>Furthermore, rt_mutex_start_proxy_lock() should not be calling into remove_waiter()
>upon a successfully grabbing the rtmutex. 1a1fb985f2e2 ("futex: Handle early deadlock
>return correctly"), moved the remove_waiter() out of __rt_mutex_start_proxy_lock()
>(where 'ret' was only ever 0 or < 0) into the wrapper. Tighten this check to
>account for try_to_take_rt_mutex().
>
>Fixes: 3bfdc63936dd ("rtmutex: Use waiter::task instead of current in remove_waiter()")
>Link: https://lore.kernel.org/all/69f114ac.050a0220.ac8b.0003.GAE@google.com/
>Reported-by: syzbot+78147abe6c524f183ee9@syzkaller.appspotmail.com
>Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
>---
> kernel/locking/rtmutex.c | 3 +++
> kernel/locking/rtmutex_api.c | 2 +-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
>diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
>index 4f386ea6c792..daeeeef973e2 100644
>--- a/kernel/locking/rtmutex.c
>+++ b/kernel/locking/rtmutex.c
>@@ -1558,6 +1558,9 @@ static void __sched remove_waiter(struct rt_mutex_base *lock,
>
> lockdep_assert_held(&lock->wait_lock);
>
>+ if (!waiter_task) /* never enqueued */
>+ return;
>+
> scoped_guard(raw_spinlock, &waiter_task->pi_lock) {
> rt_mutex_dequeue(lock, waiter);
> waiter_task->pi_blocked_on = NULL;
>diff --git a/kernel/locking/rtmutex_api.c b/kernel/locking/rtmutex_api.c
>index 124219aea46e..514fce7a4e0a 100644
>--- a/kernel/locking/rtmutex_api.c
>+++ b/kernel/locking/rtmutex_api.c
>@@ -365,7 +365,7 @@ int __sched rt_mutex_start_proxy_lock(struct rt_mutex_base *lock,
>
> raw_spin_lock_irq(&lock->wait_lock);
> ret = __rt_mutex_start_proxy_lock(lock, waiter, task, &wake_q);
>- if (unlikely(ret))
>+ if (unlikely(ret < 0))
> remove_waiter(lock, waiter);
> preempt_disable();
> raw_spin_unlock_irq(&lock->wait_lock);
>--
>2.39.5
>
next prev parent reply other threads:[~2026-06-03 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 11:29 Davidlohr Bueso
2026-06-03 14:03 ` Davidlohr Bueso [this message]
2026-06-03 20:16 ` [tip: locking/urgent] " tip-bot2 for Davidlohr Bueso
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=20260603140354.pluitgpliv6fl6fi@offworld \
--to=dave@stgolabs.net \
--cc=keenanat2000@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+78147abe6c524f183ee9@syzkaller.appspotmail.com \
--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®