From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v4 0/2] Squash to "implement mptcp read_sock" v8
Date: Fri, 11 Jul 2025 09:36:04 +0800 [thread overview]
Message-ID: <cover.1752197546.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v4:
- No need to handle "SOCK_DONE" in MPTCP, drop "SOCK_DONE" checks in
mptcp_recvmsg and mptcp_splice_read.
v3:
- rename mptcp_recv_should_stop to tcp_recv_should_stop and use it for
TCP too.
v2:
- use mptcp_recv_should_stop instead of
if (sk->sk_err ||
sk->sk_state == TCP_CLOSE ||
(sk->sk_shutdown & RCV_SHUTDOWN) ||
!timeo ||
signal_pending(current))
in mptcp_recvmsg.
- use mptcp_recv_should_stop instead of
if (sk->sk_err || sk->sk_state == TCP_CLOSE ||
(sk->sk_shutdown & RCV_SHUTDOWN) ||
signal_pending(current))
in mptcp_splice_read.
v1:
Drop "shutdown" parameter of mptcp_recv_should_stop.
Based-on: <cover.1752045499.git.tanggeliang@kylinos.cn>
Geliang Tang (2):
Squash to "mptcp: add recv_should_stop helper"
Squash to "mptcp: implement .splice_read"
include/net/tcp.h | 23 ++++++++++++++
net/ipv4/tcp.c | 73 +++++++-----------------------------------
net/mptcp/protocol.c | 75 +++++++++++++++-----------------------------
3 files changed, 59 insertions(+), 112 deletions(-)
--
2.48.1
next reply other threads:[~2025-07-11 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 1:36 Geliang Tang [this message]
2025-07-11 1:36 ` [PATCH mptcp-next v4 1/2] Squash to "mptcp: add recv_should_stop helper" Geliang Tang
2025-07-11 1:36 ` [PATCH mptcp-next v4 2/2] Squash to "mptcp: implement .splice_read" Geliang Tang
2025-07-11 7:26 ` [PATCH mptcp-next v4 0/2] Squash to "implement mptcp read_sock" v8 MPTCP CI
2025-07-11 8:44 ` MPTCP CI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1752197546.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.