This brings (hopefully) the final bits required to address the
data transfer stall reported by Geliang and Gang 

This series improves mptcp retranmission to make them reliable:
pruning can require some of them.

The only change over the previous iteration is in patch 2, addressing
 sashiko feedback over the previous iteration (possible infinite rtx
loop).

Paolo Abeni (2):
  mptcp: move the retrans loop to a separate helper
  mptcp: let the retrans scheduler do its job.

 net/mptcp/protocol.c | 155 +++++++++++++++++++++++++++++++------------
 1 file changed, 111 insertions(+), 44 deletions(-)

-- 
2.54.0

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

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


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)

Hi Paolo,

On 03/06/2026 19:47, Paolo Abeni wrote:
> This brings (hopefully) the final bits required to address the
> data transfer stall reported by Geliang and Gang 
> 
> This series improves mptcp retranmission to make them reliable:
> pruning can require some of them.
> 
> The only change over the previous iteration is in patch 2, addressing
>  sashiko feedback over the previous iteration (possible infinite rtx
> loop).
Thank you for the new version!

Now in our tree (applied before "mptcp: explicitly drop over memory
limits"):

New patches for t/upstream:
- be1684baf0a2: mptcp: move the retrans loop to a separate helper
- 9851d9d1f26c: mptcp: let the retrans scheduler do its job
- Results: bbaffa2dac1b..148c8fb6decf (export)

Tests are now in progress:

- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/9c934666a4f898f1271d5788617d3ccb1d5e600a/checks

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.