[PATCH mptcp-net 0/2] mptcp: pm: avoid sending RM_ADDR over the same subflow

Matthieu Baerts (NGI0) posted 2 patches 1 week, 3 days ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/20260219-mptcp-issue-612-v1-0-839e20d96fe7@kernel.org
There is a newer version of this series
net/mptcp/pm.c                                  | 52 +++++++++++++++++++------
tools/testing/selftests/net/mptcp/mptcp_join.sh | 36 +++++++++++++++++
2 files changed, 77 insertions(+), 11 deletions(-)
[PATCH mptcp-net 0/2] mptcp: pm: avoid sending RM_ADDR over the same subflow
Posted by Matthieu Baerts (NGI0) 1 week, 3 days ago
This should close the issue 612 reported by Frank Lorenz:

- Patch 1: avoid sending RM_ADDR over the same subflow as the one going
  to be removed.

- Patch 2: validate that in the MPTCP Join selftest.

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (2):
      mptcp: pm: avoid sending RM_ADDR over same subflow
      mptcp: pm: avoid sending RM_ADDR over same subflow

 net/mptcp/pm.c                                  | 52 +++++++++++++++++++------
 tools/testing/selftests/net/mptcp/mptcp_join.sh | 36 +++++++++++++++++
 2 files changed, 77 insertions(+), 11 deletions(-)
---
base-commit: 9bf535999bf8e23b5f38fffb1a7ae7ee73115e98
change-id: 20260219-mptcp-issue-612-d94095f11d0e

Best regards,
-- 
Matthieu Baerts (NGI0) <matttbe@kernel.org>
Re: [PATCH mptcp-net 0/2] mptcp: pm: avoid sending RM_ADDR over the same subflow
Posted by MPTCP CI 1 week, 3 days ago
Hi Matthieu,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal (except selftest_mptcp_join): Success! ✅
- KVM Validation: normal (only selftest_mptcp_join): Success! ✅
- KVM Validation: debug (except selftest_mptcp_join): Success! ✅
- KVM Validation: debug (only selftest_mptcp_join): Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/22196601516

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/b9e12177fa11
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=1055636


If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:

    $ cd [kernel source code]
    $ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
        --pull always mptcp/mptcp-upstream-virtme-docker:latest \
        auto-normal

For more details:

    https://github.com/multipath-tcp/mptcp-upstream-virtme-docker


Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)