From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: pabeni@redhat.com, kuba@kernel.org, martineau@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mptcp: fix snd_wnd initialization for passive socket" failed to apply to 5.15-stable tree
Date: Mon, 4 Mar 2024 17:37:13 +0100 [thread overview]
Message-ID: <2024030403-dubbed-singer-5c5a@gregkh> (raw)
In-Reply-To: <edc84ad2-61b0-4f17-8825-f1074c386bd4@kernel.org>
On Mon, Mar 04, 2024 at 05:13:29PM +0100, Matthieu Baerts wrote:
> Hi Greg,
>
> On 04/03/2024 10:30, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.15-stable tree.
>
> (...)
>
> > ------------------ original commit in Linus's tree ------------------
> >
> > From adf1bb78dab55e36d4d557aa2fb446ebcfe9e5ce Mon Sep 17 00:00:00 2001
> > From: Paolo Abeni <pabeni@redhat.com>
> > Date: Fri, 23 Feb 2024 17:14:15 +0100
> > Subject: [PATCH] mptcp: fix snd_wnd initialization for passive socket
> >
> > Such value should be inherited from the first subflow, but
> > passive sockets always used 'rsk_rcv_wnd'.
> >
> > Fixes: 6f8a612a33e4 ("mptcp: keep track of advertised windows right edge")
>
> This commit depends on commit 7e8b88ec35ee ("mptcp: consolidate passive
> msk socket initialization") which has apparently not been backported to
> v5.15 due to a too long list of dependences.
>
> Even if it would be better to have this fix, I don't think it is worth
> having it in v5.15.
Thanks for looking into this and letting us know.
greg k-h
prev parent reply other threads:[~2024-03-04 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 9:30 FAILED: patch "[PATCH] mptcp: fix snd_wnd initialization for passive socket" failed to apply to 5.15-stable tree gregkh
2024-03-04 16:13 ` Matthieu Baerts
2024-03-04 16:37 ` 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=2024030403-dubbed-singer-5c5a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--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