From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: lukas@wunner.de, ignat@linux.win, jarkko@kernel.org,
yimingqian591@gmail.com, stable@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] lib/crypto: mpi: Fix integer underflow in" failed to apply to 6.1-stable tree
Date: Wed, 13 May 2026 12:34:38 +0200 [thread overview]
Message-ID: <2026051334-showgirl-hurdle-22eb@gregkh> (raw)
In-Reply-To: <20260513025130.GA3110@sol>
On Tue, May 12, 2026 at 07:51:30PM -0700, Eric Biggers wrote:
> [+Cc linux-crypto@vger.kernel.org]
>
> On Tue, May 12, 2026 at 04:01:23PM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.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-6.1.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 8c2f1288250a90a4b5cabed5d888d7e3aeed4035
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026051223-undercoat-reps-6626@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..
> >
> > Possible dependencies:
>
> A couple issues. First, this email wasn't sent to the subsystem's
> mailing list (linux-crypto@vger.kernel.org in this case). That greatly
> reduces the number of people who are made aware that this didn't get
> automatically backported.
We never send out these FAILED emails to the mailing lists, as that
would make just even more noise. It's always been this way, sorry.
> Second, the upstream commit cherry-picks to 6.1, 5.15, and 5.10 without
> conflict. (The file being changed was renamed between 6.1 and 6.6, but
> 'git cherry-pick' handles that automatically.)
>
> I don't know what you're doing exactly that caused it to be
> unnecessarily marked as FAILED. But whatever it is, it's not working,
> and it is causing backports to be missed.
We don't use git for cherry-picking as we have a patch queue, so renames
will often times fail, like it did here. This has always been the case
in the decades we have been running the stable kernels :)
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-13 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2026051223-undercoat-reps-6626@gregkh>
2026-05-13 2:51 ` FAILED: patch "[PATCH] lib/crypto: mpi: Fix integer underflow in" failed to apply to 6.1-stable tree Eric Biggers
2026-05-13 10:34 ` Greg KH [this message]
2026-05-13 17:04 ` Eric Biggers
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=2026051334-showgirl-hurdle-22eb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers@kernel.org \
--cc=ignat@linux.win \
--cc=jarkko@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=stable@vger.kernel.org \
--cc=yimingqian591@gmail.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