[PATCH mptcp-next v3 0/2] patches for new MPTCP subflow subtest

Geliang Tang posted 2 patches 5 months, 1 week ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1715472312.git.tanggeliang@kylinos.cn
There is a newer version of this series
MAINTAINERS                                    |  2 +-
tools/testing/selftests/bpf/Makefile           |  2 +-
tools/testing/selftests/bpf/mptcp_pm_nl_ctl.c  |  1 +
tools/testing/selftests/bpf/prog_tests/mptcp.c | 17 ++++++-----------
4 files changed, 9 insertions(+), 13 deletions(-)
create mode 120000 tools/testing/selftests/bpf/mptcp_pm_nl_ctl.c
[PATCH mptcp-next v3 0/2] patches for new MPTCP subflow subtest
Posted by Geliang Tang 5 months, 1 week ago
From: Geliang Tang <tanggeliang@kylinos.cn>

v3:
 - update MAINTAINERS.
 - drop '-M' in _ss_search() as Matt suggested.

v2:
 - rename pm_nl_ctl to mptcp_pm_nl_ctl.


Geliang Tang (2):
  selftests/bpf: Add mptcp pm_nl_ctl link
  Squash to "selftests/bpf: Add mptcp subflow subtest"

 MAINTAINERS                                    |  2 +-
 tools/testing/selftests/bpf/Makefile           |  2 +-
 tools/testing/selftests/bpf/mptcp_pm_nl_ctl.c  |  1 +
 tools/testing/selftests/bpf/prog_tests/mptcp.c | 17 ++++++-----------
 4 files changed, 9 insertions(+), 13 deletions(-)
 create mode 120000 tools/testing/selftests/bpf/mptcp_pm_nl_ctl.c

-- 
2.43.0
Re: [PATCH mptcp-next v3 0/2] patches for new MPTCP subflow subtest
Posted by MPTCP CI 5 months, 1 week ago
Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal: Success! ✅
- KVM Validation: debug: Success! ✅
- KVM Validation: btf (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/9047431345

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


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)