[PATCH mptcp-net 0/2] mptcp: pm: in-kernel: fix issue 606

Matthieu Baerts (NGI0) posted 2 patches 20 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/20251215-issue-606-mark-subflow-endp-avail-v1-0-2f1b36da8993@kernel.org
net/mptcp/pm_kernel.c | 28 +++++++++++-----------------
1 file changed, 11 insertions(+), 17 deletions(-)
[PATCH mptcp-net 0/2] mptcp: pm: in-kernel: fix issue 606
Posted by Matthieu Baerts (NGI0) 20 hours ago
The first patch fixes it, the other one clarify the code. I think both
can go to -net.

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (2):
      mptcp: pm: in-kernel: always set as unavail when removing addr
      mptcp: pm: in-kernel: clarify mptcp_pm_remove_anno_addr()

 net/mptcp/pm_kernel.c | 28 +++++++++++-----------------
 1 file changed, 11 insertions(+), 17 deletions(-)
---
base-commit: 6be713e13dde6d9eb7f5b738db8643a9c9440ac5
change-id: 20251212-issue-606-mark-subflow-endp-avail-ccc3322ff800

Best regards,
-- 
Matthieu Baerts (NGI0) <matttbe@kernel.org>
Re: [PATCH mptcp-net 0/2] mptcp: pm: in-kernel: fix issue 606
Posted by MPTCP CI 19 hours 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): Unstable: 1 failed test(s): selftest_simult_flows 🔴
- 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/20242032173

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


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)