From: Matthieu Baerts <matttbe@kernel.org>
To: gregkh@linuxfoundation.org, pabeni@redhat.com,
davem@davemloft.net, martineau@kernel.org
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mptcp: corner case locking for rx path fields initialization" failed to apply to 6.1-stable tree
Date: Tue, 27 Feb 2024 15:46:44 +0100 [thread overview]
Message-ID: <02b2bef3-f6c9-4561-88e1-4dbcd6d5830f@kernel.org> (raw)
In-Reply-To: <2024021904-carol-mullets-5f01@gregkh>
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 e4a0fa47e816e186f6b4c0055d07eeec42d11871 Mon Sep 17 00:00:00 2001
> From: Paolo Abeni <pabeni@redhat.com>
> Date: Thu, 8 Feb 2024 19:03:52 +0100
> Subject: [PATCH] mptcp: corner case locking for rx path fields initialization
>
> Most MPTCP-level related fields are under the mptcp data lock
> protection, but are written one-off without such lock at MPC
> complete time, both for the client and the server
>
> Leverage the mptcp_propagate_state() infrastructure to move such
> initialization under the proper lock client-wise.
>
> The server side critical init steps are done by
> mptcp_subflow_fully_established(): ensure the caller properly held the
> relevant lock, and avoid acquiring the same lock in the nested scopes.
>
> There are no real potential races, as write access to such fields
> is implicitly serialized by the MPTCP state machine; the primary
> goal is consistency.
FYI, because of the various conflicts, and because "there are no real
potential races", with Paolo, we think it is best not to backport this
patch to v6.1 and older.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-02-27 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:05 FAILED: patch "[PATCH] mptcp: corner case locking for rx path fields initialization" failed to apply to 6.1-stable tree gregkh
2024-02-27 14:46 ` Matthieu Baerts [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=02b2bef3-f6c9-4561-88e1-4dbcd6d5830f@kernel.org \
--to=matttbe@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=martineau@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