From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: pabeni@redhat.com, davem@davemloft.net, martineau@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mptcp: fix more tx path fields initialization" failed to apply to 6.1-stable tree
Date: Tue, 27 Feb 2024 16:27:18 +0100 [thread overview]
Message-ID: <2024022704-reflector-conducive-6b5c@gregkh> (raw)
In-Reply-To: <a9e6e10d-9d91-4ec8-b803-4df079ca68e3@kernel.org>
On Tue, Feb 27, 2024 at 03:47:01PM +0100, Matthieu Baerts wrote:
> Hi Greg,
>
> On 19/02/2024 17:05, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.1-stable tree.
>
> (...)
>
> > From 3f83d8a77eeeb47011b990fd766a421ee64f1d73 Mon Sep 17 00:00:00 2001
> > From: Paolo Abeni <pabeni@redhat.com>
> > Date: Thu, 8 Feb 2024 19:03:51 +0100
> > Subject: [PATCH] mptcp: fix more tx path fields initialization
> >
> > The 'msk->write_seq' and 'msk->snd_nxt' are always updated under
> > the msk socket lock, except at MPC handshake completiont time.
> >
> > Builds-up on the previous commit to move such init under the relevant
> > lock.
> >
> > There are no known problems caused by the potential race, the
> > primary goal is consistency.
>
> FYI, because of the various conflicts, and because "there are no known
> problems caused by the potential race", with Paolo, we think it is best
> not to backport this patch to v6.1 and older.
Thanks for the review of all of these and letting us know,
greg k-h
prev parent reply other threads:[~2024-02-27 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:05 FAILED: patch "[PATCH] mptcp: fix more tx path fields initialization" failed to apply to 6.1-stable tree gregkh
2024-02-27 14:47 ` Matthieu Baerts
2024-02-27 15:27 ` 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=2024022704-reflector-conducive-6b5c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--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