[RFC mptcp-next v3 0/8] MPTCP KTLS support

Geliang Tang posted 8 patches 5 days, 2 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1763800601.git.tanggeliang@kylinos.cn
include/net/mptcp.h                           |  33 +++++
net/mptcp/protocol.c                          |  62 +++++++--
net/mptcp/sockopt.c                           |  30 ++++-
net/tls/tls_device.c                          |   8 +-
net/tls/tls_main.c                            |   6 +-
net/tls/tls_strp.c                            |  16 ++-
net/tls/tls_sw.c                              |   4 +-
tools/testing/selftests/net/mptcp/config      |   1 +
.../selftests/net/mptcp/mptcp_connect.c       |  36 +++--
.../selftests/net/mptcp/mptcp_sockopt.c       | 125 ++++++++++++++++--
.../selftests/net/mptcp/mptcp_sockopt.sh      |  36 +++++
11 files changed, 315 insertions(+), 42 deletions(-)
[RFC mptcp-next v3 0/8] MPTCP KTLS support
Posted by Geliang Tang 5 days, 2 hours ago
From: Geliang Tang <tanggeliang@kylinos.cn>

v3:
 - mptcp_read_sock() and mptcp_poll() are not exported, as mptcp_sockopt
   test does not use read_sock/poll interfaces. They will be exported when
   new tests are added in the future.
 - call mptcp_inq_hint in tls_device_rx_resync_new_rec(),
   tls_device_core_ctrl_rx_resync() and tls_read_flush_backlog() too.
 - update selftests. 

v2:
 - fix disconnect.
 - update selftests.

This series adds KTLS support for MPTCP. Since the ULP of msk is not being
used, ULP KTLS can be directly configured onto msk without affecting its
communication.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/480

Depends on: implement mptcp read_sock, v13
Based-on: <cover.1761198660.git.geliang@kernel.org>

Geliang Tang (8):
  selftests: mptcp: sockopt: add protocol arguments
  selftests: mptcp: sockopt: enhance compatibility with TCP tests
  selftests: mptcp: sockopt: implement TCP TLS tests
  tls: add MPTCP protocol support
  mptcp: update ULP getsockopt
  mptcp: enable TLS setsockopt
  selftests: mptcp: connect: update sock_test_tcpulp
  selftests: mptcp: sockopt: cover MPTCP KTLS test cases

 include/net/mptcp.h                           |  33 +++++
 net/mptcp/protocol.c                          |  62 +++++++--
 net/mptcp/sockopt.c                           |  30 ++++-
 net/tls/tls_device.c                          |   8 +-
 net/tls/tls_main.c                            |   6 +-
 net/tls/tls_strp.c                            |  16 ++-
 net/tls/tls_sw.c                              |   4 +-
 tools/testing/selftests/net/mptcp/config      |   1 +
 .../selftests/net/mptcp/mptcp_connect.c       |  36 +++--
 .../selftests/net/mptcp/mptcp_sockopt.c       | 125 ++++++++++++++++--
 .../selftests/net/mptcp/mptcp_sockopt.sh      |  36 +++++
 11 files changed, 315 insertions(+), 42 deletions(-)

-- 
2.51.0
Re: [RFC mptcp-next v3 0/8] MPTCP KTLS support
Posted by MPTCP CI 4 days, 23 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): Unstable: 1 failed test(s): packetdrill_dss 🔴
- 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/19593304037

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


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)