From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y 1/6] selftests: mptcp: add missing join check
Date: Thu, 31 Jul 2025 18:19:15 -0400 [thread overview]
Message-ID: <1753975897-9b286fab@stable.kernel.org> (raw)
In-Reply-To: <20250731112353.2638719-9-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: 857898eb4b28daf3faca3ae334c78b2bb141475e
WARNING: Author mismatch between patch and upstream commit:
Backport author: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Commit author: Matthieu Baerts <matthieu.baerts@tessares.net>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: 857898eb4b28 ! 1: 37fd6152bfd5 selftests: mptcp: add missing join check
@@ Metadata
## Commit message ##
selftests: mptcp: add missing join check
+ commit 857898eb4b28daf3faca3ae334c78b2bb141475e upstream.
+
This function also writes the name of the test with its ID, making clear
a new test has been executed.
@@ Commit message
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+ [ Conflict in mptcp_join.sh, because commit 86e39e04482b ("mptcp: keep
+ track of local endpoint still available for each msk") is not in this
+ version and changed the context. The same line can still be applied at
+ the same place. ]
+ Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
## tools/testing/selftests/net/mptcp/mptcp_join.sh ##
@@ tools/testing/selftests/net/mptcp/mptcp_join.sh: signal_address_tests()
@@ tools/testing/selftests/net/mptcp/mptcp_join.sh: signal_address_tests()
ip netns exec $ns2 ./pm_nl_ctl add 10.0.4.2 flags signal
run_tests $ns1 $ns2 10.0.1.1
+ chk_join_nr "signal addresses race test" 3 3 3
+ chk_add_nr 4 4
+ }
- # the server will not signal the address terminating
- # the MPC subflow
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 5.15 | Success | Success |
next prev parent reply other threads:[~2025-07-31 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 11:23 [PATCH 5.15.y 0/6] Old missing backports Matthieu Baerts (NGI0)
2025-07-31 11:23 ` [PATCH 5.15.y 1/6] selftests: mptcp: add missing join check Matthieu Baerts (NGI0)
2025-07-31 22:19 ` Sasha Levin [this message]
2025-08-22 13:44 ` Patch "selftests: mptcp: add missing join check" has been added to the 5.15-stable tree gregkh
2025-07-31 11:23 ` [PATCH 5.15.y 2/6] mptcp: fix error mibs accounting Matthieu Baerts (NGI0)
2025-07-31 22:20 ` Sasha Levin
2025-08-22 13:44 ` Patch "mptcp: fix error mibs accounting" has been added to the 5.15-stable tree gregkh
2025-07-31 11:23 ` [PATCH 5.15.y 3/6] mptcp: introduce MAPPING_BAD_CSUM Matthieu Baerts (NGI0)
2025-07-31 22:20 ` Sasha Levin
2025-08-22 13:44 ` Patch "mptcp: introduce MAPPING_BAD_CSUM" has been added to the 5.15-stable tree gregkh
2025-07-31 11:23 ` [PATCH 5.15.y 4/6] selftests: mptcp: Initialize variables to quiet gcc 12 warnings Matthieu Baerts (NGI0)
2025-07-31 22:19 ` Sasha Levin
2025-08-22 13:44 ` Patch "selftests: mptcp: Initialize variables to quiet gcc 12 warnings" has been added to the 5.15-stable tree gregkh
2025-07-31 11:23 ` [PATCH 5.15.y 5/6] mptcp: drop unused sk in mptcp_push_release Matthieu Baerts (NGI0)
2025-07-31 22:20 ` Sasha Levin
2025-08-22 13:44 ` Patch "mptcp: drop unused sk in mptcp_push_release" has been added to the 5.15-stable tree gregkh
2025-07-31 11:24 ` [PATCH 5.15.y 6/6] mptcp: do not queue data on closed subflows Matthieu Baerts (NGI0)
2025-07-31 22:19 ` Sasha Levin
2025-08-22 13:44 ` Patch "mptcp: do not queue data on closed subflows" has been added to the 5.15-stable tree gregkh
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=1753975897-9b286fab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.