[PATCH mptcp-net v3 0/3] mptcp: fix stall because of data_ready

Gang Yan posted 3 patches 4 days, 22 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1773735950.git.yangang@kylinos.cn
net/mptcp/protocol.c | 93 +++++++++++++++++++++++++++++++++++++-------
net/mptcp/protocol.h |  2 +-
2 files changed, 81 insertions(+), 14 deletions(-)
[PATCH mptcp-net v3 0/3] mptcp: fix stall because of data_ready
Posted by Gang Yan 4 days, 22 hours ago
From: Gang Yan <yangang@kylinos.cn>

Hi Paolo,Matt:

The patches have replaced the original backlog_list with an rb-tree based
'backlog_queue', and resolved the existing transmission stall issues by using
the new backlog_queue infrastructure.

Looking forward to your comments and feedback.

Thanks
Gang

Gang Yan (3):
  mptcp: replace backlog_list with backlog_queue
  mptcp: fix the stall problems using backlog_queue
  mptcp: fix the stall problems with data_ready

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

-- 
2.43.0
Re: [PATCH mptcp-net v3 0/3] mptcp: fix stall because of data_ready
Posted by MPTCP CI 4 days, 20 hours ago
Hi Gang,

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): Unstable: 1 failed test(s): packetdrill_mp_capable 🔴
- 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/23186215138

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


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)