From: Thomas Gleixner <tglx@kernel.org>
To: gregkh@linuxfoundation.org, yaokai34@huawei.com, peterz@infradead.org
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] futex: Fix race in futex_pivot_pending() during private hash" failed to apply to 7.1-stable tree
Date: Fri, 14 Aug 2026 14:10:01 +0200 [thread overview]
Message-ID: <87a4qonbs6.ffs@fw13> (raw)
In-Reply-To: <2026081352-debate-broadband-ab5e@gregkh>
On Thu, Aug 13 2026 at 09:52, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 7.1-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> To reproduce the conflict and resubmit, you may use the following commands:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-7.1.y
> git checkout FETCH_HEAD
> git cherry-pick -x 8e7ff730dd96519a333d1570edf1c3fabb6d3629
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026081352-debate-broadband-ab5e@gregkh' --subject-prefix 'PATCH 7.1.y' 'HEAD^..'
>
> Possible dependencies:
>
>
>
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> From 8e7ff730dd96519a333d1570edf1c3fabb6d3629 Mon Sep 17 00:00:00 2001
> From: Yao Kai <yaokai34@huawei.com>
> Date: Tue, 4 Aug 2026 20:55:30 +0800
> Subject: [PATCH] futex: Fix race in futex_pivot_pending() during private hash
> resize
Don't backport. It's broken.
prev parent reply other threads:[~2026-08-14 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 0:52 FAILED: patch "[PATCH] futex: Fix race in futex_pivot_pending() during private hash" failed to apply to 7.1-stable tree gregkh
2026-08-14 12:10 ` 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=87a4qonbs6.ffs@fw13 \
--to=tglx@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=yaokai34@huawei.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