From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: pabeni@redhat.com, cpaasch@apple.com, kuba@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mptcp: fix possible divide by zero in recvmsg()" failed to apply to 5.10-stable tree
Date: Thu, 29 Jun 2023 20:07:48 +0200 [thread overview]
Message-ID: <2023062938-tidbit-sampling-3bde@gregkh> (raw)
In-Reply-To: <062b7104-b536-2b09-acae-3f99d57368dd@tessares.net>
On Thu, Jun 29, 2023 at 08:00:29PM +0200, Matthieu Baerts wrote:
> Hi Greg,
>
> On 23/06/2023 11:30, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.10-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-5.10.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 0ad529d9fd2bfa3fc619552a8d2fb2f2ef0bce2e
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023062349-nerd-rupture-49ab@gregkh' --subject-prefix 'PATCH 5.10.y' HEAD^..
>
> Thank you for the notification.
>
> I think we can drop this patch for v5.10. The infrastructure in the code
> is not there (mptcp_disconnect()) and the risk is very low: we only saw
> the issue recently, maybe only visible in newer versions due to other
> features.
>
> So no need to do anything here for v5.10.
Great, thanks for letting us know.
greg k-h
prev parent reply other threads:[~2023-06-29 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 9:30 FAILED: patch "[PATCH] mptcp: fix possible divide by zero in recvmsg()" failed to apply to 5.10-stable tree gregkh
2023-06-29 18:00 ` Matthieu Baerts
2023-06-29 18:07 ` Greg KH [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=2023062938-tidbit-sampling-3bde@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cpaasch@apple.com \
--cc=kuba@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=pabeni@redhat.com \
--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