From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 3/3] mptcp: reset fallback status gracefully at disconnect() time
Date: Tue, 29 Jul 2025 17:03:07 -0400 [thread overview]
Message-ID: <1753816740-791ed0de@stable.kernel.org> (raw)
In-Reply-To: <20250728132919.3904847-8-matttbe@kernel.org>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: da9b2fc7b73d147d88abe1922de5ab72d72d7756
WARNING: Author mismatch between patch and upstream commit:
Backport author: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Commit author: Paolo Abeni <pabeni@redhat.com>
Status in newer kernel trees:
6.15.y | Not found
6.12.y | Not found
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: da9b2fc7b73d ! 1: 96832530025f mptcp: reset fallback status gracefully at disconnect() time
@@ Metadata
## Commit message ##
mptcp: reset fallback status gracefully at disconnect() time
+ commit da9b2fc7b73d147d88abe1922de5ab72d72d7756 upstream.
+
mptcp_disconnect() clears the fallback bit unconditionally, without
touching the associated flags.
@@ Commit message
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20250714-net-mptcp-fallback-races-v1-3-391aff963322@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+ [ Conflicts in protocol.c, because commit ebc1e08f01eb ("mptcp: drop
+ last_snd and MPTCP_RESET_SCHEDULER") is not in this version and
+ changed the context. The same modification can still be applied at the
+ same place. ]
+ Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
## net/mptcp/protocol.c ##
@@ net/mptcp/protocol.c: static int mptcp_disconnect(struct sock *sk, int flags)
- * subflow
*/
mptcp_destroy_common(msk, MPTCP_CF_FASTCLOSE);
+ msk->last_snd = NULL;
+
+ /* The first subflow is already in TCP_CLOSE status, the following
+ * can't overlap with a fallback anymore
@@ net/mptcp/protocol.c: static int mptcp_disconnect(struct sock *sk, int flags)
+
msk->cb_flags = 0;
msk->recovery = false;
- WRITE_ONCE(msk->can_ack, false);
+ msk->can_ack = false;
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 6.1 | Success | Success |
prev parent reply other threads:[~2025-07-29 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 13:29 [PATCH 6.1.y 0/3] mptcp: fix recent failed backports (20250721) Matthieu Baerts (NGI0)
2025-07-28 13:29 ` [PATCH 6.1.y 1/3] mptcp: make fallback action and fallback decision atomic Matthieu Baerts (NGI0)
2025-07-29 19:37 ` Sasha Levin
2025-07-28 13:29 ` [PATCH 6.1.y 2/3] mptcp: plug races between subflow fail and subflow creation Matthieu Baerts (NGI0)
2025-07-29 19:45 ` Sasha Levin
2025-07-28 13:29 ` [PATCH 6.1.y 3/3] mptcp: reset fallback status gracefully at disconnect() time Matthieu Baerts (NGI0)
2025-07-29 21:03 ` Sasha Levin [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=1753816740-791ed0de@stable.kernel.org \
--to=sashal@kernel.org \
--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