From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Peter Zijlstra <peterz@infradead.org>,
syzbot <syzbot+034246a838a10d181e78@syzkaller.appspotmail.com>,
andrealmeid@igalia.com, dave@stgolabs.net, dvhart@infradead.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] futex: Prevent use-after-free during requeue-PI
Date: Wed, 10 Sep 2025 12:48:06 +0200 [thread overview]
Message-ID: <20250910104806.Jkzd5ya1@linutronix.de> (raw)
In-Reply-To: <20250910104243.TUMt9HM0@linutronix.de>
On 2025-09-10 12:42:45 [+0200], To Thomas Gleixner wrote:
> --- a/kernel/futex/requeue.c
> +++ b/kernel/futex/requeue.c
> @@ -243,10 +244,11 @@ void requeue_pi_wake_futex(struct futex_q *q, union futex_key *key,
> futex_hash_get(hb);
> q->drop_hb_ref = true;
> q->lock_ptr = &hb->lock;
> + task = READ_ONCE(q->task);
>
> /* Signal locked state to the waiter */
> futex_requeue_pi_complete(q, 1);
once understood, adding an mdelay(500) here greatly improves the chances
to trigger.
futex_requeue_pi_complete() uses atomic_try_cmpxchg() which has full
ordering. This means that the q->drop_hb_ref assignment earlier is
visible to the other thread after that cmpxchg, correct?
> - wake_up_state(q->task, TASK_NORMAL);
> + wake_up_state(task, TASK_NORMAL);
> }
Sebastian
next prev parent reply other threads:[~2025-09-10 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 20:54 [syzbot] [kernel?] general protection fault in try_to_wake_up (3) syzbot
2025-09-02 21:46 ` Peter Zijlstra
2025-09-03 13:07 ` Sebastian Andrzej Siewior
2025-09-03 18:51 ` Jens Axboe
2025-09-04 16:28 ` Sebastian Andrzej Siewior
2025-09-09 18:56 ` Thomas Gleixner
2025-09-09 19:27 ` Jens Axboe
2025-09-09 20:43 ` Thomas Gleixner
2025-09-09 20:46 ` Jens Axboe
2025-09-10 10:42 ` [PATCH] futex: Prevent use-after-free during requeue-PI Sebastian Andrzej Siewior
2025-09-10 10:48 ` Sebastian Andrzej Siewior [this message]
2025-09-20 15:43 ` [tip: locking/urgent] " tip-bot2 for Sebastian Andrzej Siewior
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=20250910104806.Jkzd5ya1@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrealmeid@igalia.com \
--cc=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+034246a838a10d181e78@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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®