mbox series

[mptcp-next,0/3] Squash to "Add mptcp_subflow bpf_iter support"

Message ID cover.1732172851.git.tanggeliang@kylinos.cn (mailing list archive)
Headers show
Series Squash to "Add mptcp_subflow bpf_iter support" | expand

Message

Geliang Tang Nov. 21, 2024, 7:10 a.m. UTC
From: Geliang Tang <tanggeliang@kylinos.cn>

Address Martin's comments in v1.

Geliang Tang (3):
  Squash to "bpf: Register mptcp common kfunc set"
  Squash to "bpf: Add mptcp_subflow bpf_iter"
  Squash to "selftests/bpf: Add mptcp_subflow bpf_iter subtest"

 net/mptcp/bpf.c                               | 20 ++++++++++++++-----
 .../selftests/bpf/progs/mptcp_bpf_iters.c     |  7 +++----
 2 files changed, 18 insertions(+), 9 deletions(-)

Comments

MPTCP CI Nov. 21, 2024, 7:31 a.m. UTC | #1
Hi Geliang,

Thank you for your modifications, that's great!

But sadly, our CI spotted some issues with it when trying to build it.

You can find more details there:

  https://github.com/multipath-tcp/mptcp_net-next/actions/runs/11948563035

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

Feel free to reply to this email if you cannot access logs, if you need
some support to fix the error, if this doesn't seem to be caused by your
modifications or if the error is a false positive one.

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
MPTCP CI Nov. 21, 2024, 8:20 a.m. UTC | #2
Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

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

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


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)