[PATCH mptcp-next v2 0/3] mptcp: add more sockopts

Geliang Tang posted 3 patches 1 month ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1754986785.git.tanggeliang@kylinos.cn
net/mptcp/sockopt.c | 54 +++++++++++++++++++++++++++++++++++++++++----
1 file changed, 50 insertions(+), 4 deletions(-)
[PATCH mptcp-next v2 0/3] mptcp: add more sockopts
Posted by Geliang Tang 1 month ago
From: Geliang Tang <tanggeliang@kylinos.cn>

v2:
 - Use and extend mptcp_setsockopt_all_sf to remove duplicate code in v1

Depends on:
 - refactor MPTCP socket option handling

Based-on: <cover.1754986557.git.tanggeliang@kylinos.cn>

v1:
https://patchwork.kernel.org/project/mptcp/cover/cover.1754126092.git.tanggeliang@kylinos.cn/

Add sockopt support for IPV6_TCLASS, IP_TTL and IPV6_UNICAST_HOPS.

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

Geliang Tang (3):
  mptcp: add IPV6_TCLASS socket option support
  mptcp: add IP_TTL socket option support
  mptcp: add IPV6_UNICAST_HOPS socket option support

 net/mptcp/sockopt.c | 54 +++++++++++++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 4 deletions(-)

-- 
2.48.1
Re: [PATCH mptcp-next v2 0/3] mptcp: add more sockopts
Posted by MPTCP CI 1 month ago
Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal: Unstable: 1 failed test(s): selftest_mptcp_connect_checksum 🔴
- KVM Validation: debug: Unstable: 1 failed test(s): packetdrill_mp_capable 🔴
- 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/16903540842

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


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)