| Message ID | cover.1740638334.git.tanggeliang@kylinos.cn (mailing list archive) |
|---|---|
| Headers | show |
| Series | BPF path manager, part 5 | expand |
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/13560646576 Status: failure Initiator: Patchew Applier Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/2fc0cce80faf Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=938355 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)
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-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/13560646466
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/2fc0cce80faf
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=938355
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)
From: Geliang Tang <tanggeliang@kylinos.cn> Some path manager related refactoring and cleanups. - patch 1, a cleanup. - patches 2-4, drop mptcp_pm_is_userspace() and mptcp_pm_is_kernel(). - patches 5-6, change remote of set_flags as mptcp_pm_addr_entry type. Geliang Tang (6): mptcp: pm: use pm variable instead of msk->pm mptcp: pm: userspace: drop is_userspace in free_local_addr_list mptcp: pm: drop is_kernel in alloc_anno_list mptcp: pm: in-kernel: drop is_userspace in remove_id_zero mptcp: pm: add remote parameter for set_flags mptcp: pm: in-kernel: drop changed parameter of set_flags net/mptcp/pm.c | 28 ++++++++---- net/mptcp/pm_netlink.c | 93 +++++++++++++++++++++------------------- net/mptcp/pm_userspace.c | 25 +++-------- net/mptcp/protocol.h | 5 ++- 4 files changed, 77 insertions(+), 74 deletions(-)