[PATCH mptcp-net v3 0/2] mptcp: more cleanups

Paolo Abeni posted 2 patches 1 week ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1787911017.git.pabeni@redhat.com
net/mptcp/protocol.c | 18 +++++++++++++-----
net/mptcp/protocol.h |  2 +-
2 files changed, 14 insertions(+), 6 deletions(-)
[PATCH mptcp-net v3 0/2] mptcp: more cleanups
Posted by Paolo Abeni 1 week ago
Follow-up the recent fixes, as per sashiko nipa feedback. A new
patch and an update to an exiting one.

This is basically v1 again with hopefully better changelog to avoid AI
slop review (and myself not detecting the latter as such).

Paolo Abeni (2):
  mptcp: prevent race between disconnect() and rtx
  Squash-to: "mptcp: do not reschedule the RTX timer for fallback
    sockets"

 net/mptcp/protocol.c | 18 +++++++++++++-----
 net/mptcp/protocol.h |  2 +-
 2 files changed, 14 insertions(+), 6 deletions(-)

-- 
2.55.0
Re: [PATCH mptcp-net v3 0/2] mptcp: more cleanups
Posted by Matthieu Baerts 1 week ago
Hi Paolo,

On 28/08/2026 12:17, Paolo Abeni wrote:
> Follow-up the recent fixes, as per sashiko nipa feedback. A new
> patch and an update to an exiting one.

Thank you for the fixes!

New patches for t/upstream-net and t/upstream:
- f95e1533532b: "squashed" patch 2/2 in "mptcp: do not reschedule the
RTX timer for fallback sockets"
- 7951c9d65b6f: mptcp: prevent race between disconnect() and rtx
- 0057523d4132: tg:msg: appended explanations for reviewers
- Results: d4a0635cd6fc..bb60157d0392 (export-net)
- Results: d92f7d553a9b..c5eb9a747a9a (export)

Tests are now in progress:

- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/1db74a6e22390b0bc05dc9c57f8af7ef3edb4c63/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/39d4f32c5d534bd880ffdfe4f32499379a7ccd01/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.
Re: [PATCH mptcp-net v3 0/2] mptcp: more cleanups
Posted by MPTCP CI 1 week ago
Hi Paolo,

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/33164019952

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


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)