Message ID | 20240530131308.59737-1-kerneljasonxing@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | tcp/mptcp: count CLOSE-WAIT for CurrEstab | expand |
Hi Jason, 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/9303441254 Initiator: Patchew Applier Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/7f7bd9b64def Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=857361 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: Jason Xing <kernelxing@tencent.com> Taking CLOSE-WAIT sockets into CurrEstab counters is in accordance with RFC 1213, as suggested by Eric and Neal. Previous discussion Link: https://lore.kernel.org/all/20240529033104.33882-1-kerneljasonxing@gmail.com/ Jason Xing (2): tcp: count CLOSE-WAIT sockets for TCP_MIB_CURRESTAB mptcp: count CLOSE-WAIT sockets for MPTCP_MIB_CURRESTAB net/ipv4/tcp.c | 6 +++++- net/mptcp/protocol.c | 5 +++-- 2 files changed, 8 insertions(+), 3 deletions(-)