[PATCH mptcp-next v2 0/2] add tcp_recv_should_stop helper

Geliang Tang posted 2 patches 3 days, 23 hours ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/multipath-tcp/mptcp_net-next tags/patchew/cover.1770089761.git.tanggeliang@kylinos.cn
include/net/tcp.h    |  9 +++++++++
net/ipv4/tcp.c       | 10 ++--------
net/mptcp/protocol.c | 12 ++++--------
3 files changed, 15 insertions(+), 16 deletions(-)
[PATCH mptcp-next v2 0/2] add tcp_recv_should_stop helper
Posted by Geliang Tang 3 days, 23 hours ago
From: Geliang Tang <tanggeliang@kylinos.cn>

Two cleanups for "implement read_sock" series.

v2:
 - v1 changed the original behavior when replacing tcp_recv_should_stop.
   This version preserves the behavior unchanged.
 - add a cleanup patch for read_sock into this set.

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

Gang Yan (1):
  mptcp: check desc->count in read_sock

Geliang Tang (1):
  tcp: add recv_should_stop helper

 include/net/tcp.h    |  9 +++++++++
 net/ipv4/tcp.c       | 10 ++--------
 net/mptcp/protocol.c | 12 ++++--------
 3 files changed, 15 insertions(+), 16 deletions(-)

-- 
2.52.0
Re: [PATCH mptcp-next v2 0/2] add tcp_recv_should_stop helper
Posted by MPTCP CI 3 days, 21 hours ago
Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- KVM Validation: normal (except selftest_mptcp_join): Success! ✅
- KVM Validation: normal (only selftest_mptcp_join): Success! ✅
- KVM Validation: debug (except selftest_mptcp_join): Success! ✅
- KVM Validation: debug (only selftest_mptcp_join): Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Critical: Boot failures ❌
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/21616628959

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


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)