[PATCH mptcp-next 0/3] implement .splice_eof

Geliang Tang posted 3 patches 5 days, 4 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1770023932.git.tanggeliang@kylinos.cn
There is a newer version of this series
include/net/tcp.h                                |  1 +
net/ipv4/tcp.c                                   |  8 ++++++--
net/mptcp/protocol.c                             | 16 ++++++++++++++++
.../testing/selftests/net/mptcp/mptcp_connect.c  |  2 +-
4 files changed, 24 insertions(+), 3 deletions(-)
[PATCH mptcp-next 0/3] implement .splice_eof
Posted by Geliang Tang 5 days, 4 hours ago
From: Geliang Tang <tanggeliang@kylinos.cn>

This set implements .splice_eof for MPTCP and tests it.

Geliang Tang (3):
  tcp: export do_tcp_splice_eof
  mptcp: implement .splice_eof
  selftests: mptcp: connect: trigger splice_eof

 include/net/tcp.h                                |  1 +
 net/ipv4/tcp.c                                   |  8 ++++++--
 net/mptcp/protocol.c                             | 16 ++++++++++++++++
 .../testing/selftests/net/mptcp/mptcp_connect.c  |  2 +-
 4 files changed, 24 insertions(+), 3 deletions(-)

-- 
2.51.0
Re: [PATCH mptcp-next 0/3] implement .splice_eof
Posted by MPTCP CI 5 days, 3 hours ago
Hi Geliang,

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_dss 🔴
- 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/21584982091

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


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)