From: Thomas Gleixner <tglx@kernel.org>
To: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, keno@juliacomputing.com,
keno@juliahub.com, mingo@kernel.org
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: [PATCH 7.1.y, 6.18.y, 6.12.y] futex: Prevent robust futex exit race some more
Date: Sat, 15 Aug 2026 16:34:07 +0200 [thread overview]
Message-ID: <87se4flag0.ffs@fw13> (raw)
In-Reply-To: <20260814193000.16@kernel.org>
On Fri, Aug 14 2026 at 22:33, Sasha Levin wrote:
>> commit 6d4514ca9cdf61fec4ec634cf50386f6f7e69748 upstream.
>>
>> A robust futex unlock stores 0 over the whole futex value - wiping
>> FUTEX_WAITERS - and wakes a single waiter. That wakeup is a one-shot
>> notification: the protocol relies on its recipient to either acquire the
>> futex (and eventually unlock while aware of the remaining contention) or
>> re-arm FUTEX_WAITERS before sleeping again.
>
> Queued for all the active stable trees (7.1 down to 5.10), thanks. The older
> ones needed futex_wake()'s signature adapted; the logic is unchanged.
That's why I sent two batches. One for 7.1 - 6.12 and one for 6.6 and
older :)
prev parent reply other threads:[~2026-08-15 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 0:52 FAILED: patch "[PATCH] futex: Prevent robust futex exit race some more" failed to apply to 7.1-stable tree gregkh
2026-08-14 12:43 ` [PATCH 7.1.y, 6.18.y, 6.12.y] futex: Prevent robust futex exit race some more Thomas Gleixner
2026-08-15 2:33 ` Sasha Levin
2026-08-15 14:34 ` Thomas Gleixner [this message]
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=87se4flag0.ffs@fw13 \
--to=tglx@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keno@juliacomputing.com \
--cc=keno@juliahub.com \
--cc=mingo@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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