From: Geliang Tang <geliang@kernel.org>
To: Gang Yan <gang.yan@linux.dev>, mptcp@lists.linux.dev
Cc: pabeni@redhat.com, Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v2 2/7] mptcp: take TCP_MAXSEG handling into __mptcp_setsockopt_set_val
Date: Thu, 23 Jul 2026 09:10:01 +0800 [thread overview]
Message-ID: <f28023650f3feaec991e266ee0226c5c0110f17e.camel@kernel.org> (raw)
In-Reply-To: <11304a8f1ec63390553390404d9164f7a4213b79.1784601268.git.yangang@kylinos.cn>
Hi Gang,
On Tue, 2026-07-21 at 10:40 +0800, Gang Yan wrote:
> From: Gang Yan <yangang@kylinos.cn>
>
> mptcp_setsockopt_all_sf is only used in 'TCP_MAXSEG', and it can be
> replaced with __mptcp_setsockopt_set_val.
>
> Signed-off-by: Gang Yan <yangang@kylinos.cn>
> ---
> net/ipv4/tcp.c | 1 +
> net/mptcp/sockopt.c | 27 ++-------------------------
> 2 files changed, 3 insertions(+), 25 deletions(-)
>
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index b427f924608c..5915d0e62f43 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -3830,6 +3830,7 @@ int tcp_sock_set_maxseg(struct sock *sk, int
> val)
> WRITE_ONCE(tcp_sk(sk)->rx_opt.user_mss, val);
> return 0;
> }
> +EXPORT_SYMBOL(tcp_sock_set_maxseg);
>
> /*
> * Socket option code for TCP.
> diff --git a/net/mptcp/sockopt.c b/net/mptcp/sockopt.c
> index 9c4faa0d82ef..3e000436ab94 100644
> --- a/net/mptcp/sockopt.c
> +++ b/net/mptcp/sockopt.c
> @@ -808,28 +808,6 @@ static int mptcp_setsockopt_first_sf_only(struct
> mptcp_sock *msk, int level, int
> return ret;
> }
>
> -static int mptcp_setsockopt_all_sf(struct mptcp_sock *msk, int
> level,
> - int optname, sockptr_t optval,
> - unsigned int optlen)
> -{
> - struct mptcp_subflow_context *subflow;
> - int ret = 0;
> -
> - mptcp_for_each_subflow(msk, subflow) {
> - struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
> - int err;
> -
> - err = tcp_setsockopt(ssk, level, optname, optval,
> optlen);
> - if (err < 0 && ret == 0)
> - ret = err;
> - }
> -
> - if (!ret)
> - sockopt_seq_inc(msk);
> -
> - return ret;
> -}
This helper will also be used when implementing IPV6_TCLASS [1], so
don't delete it for now. Let's wait until IPV6_TCLASS is merged before
posting this patch.
Thanks,
-Geliang
[1]
https://patchwork.kernel.org/project/mptcp/patch/2617b8684039574734b8622936ef126d6a7cd519.1754986785.git.tanggeliang@kylinos.cn/
> -
> static int mptcp_setsockopt_sol_tcp(struct mptcp_sock *msk, int
> optname,
> sockptr_t optval, unsigned int
> optlen)
> {
> @@ -889,9 +867,8 @@ static int mptcp_setsockopt_sol_tcp(struct
> mptcp_sock *msk, int optname,
> val);
> break;
> case TCP_MAXSEG:
> - msk->maxseg = val;
> - ret = mptcp_setsockopt_all_sf(msk, SOL_TCP, optname,
> optval,
> - optlen);
> + ret = __mptcp_setsockopt_set_val(msk,
> &tcp_sock_set_maxseg,
> + &msk->maxseg, val);
> break;
> default:
> ret = -ENOPROTOOPT;
next prev parent reply other threads:[~2026-07-23 1:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 2:40 [PATCH mptcp-next v2 0/7] mptcp: add bpf_setsockopt support Gang Yan
2026-07-21 2:40 ` [PATCH mptcp-next v2 1/7] mptcp: drop unused @max arg of __mptcp_setsockopt_set_val Gang Yan
2026-07-21 2:40 ` [PATCH mptcp-next v2 2/7] mptcp: take TCP_MAXSEG handling into __mptcp_setsockopt_set_val Gang Yan
2026-07-23 1:10 ` Geliang Tang [this message]
2026-07-21 2:40 ` [PATCH mptcp-next v2 3/7] mptcp: use sockopt_lock/release_sock in sockopt Gang Yan
2026-07-21 2:40 ` [PATCH mptcp-next v2 4/7] mptcp: reject sockopt requiring ssks' lock in BPF context Gang Yan
2026-07-21 2:41 ` [PATCH mptcp-next v2 5/7] mptcp: enable bpf_setsockopt on the master socket Gang Yan
2026-07-21 2:41 ` [PATCH mptcp-next v2 6/7] mptcp: add TCP_CONNECT_CB sock_ops hook Gang Yan
2026-07-21 2:41 ` [PATCH mptcp-next v2 7/7] selftests: bpf: verify mptcp bpf_setsockopt from TCP_CONNECT_CB Gang Yan
2026-07-21 3:46 ` [PATCH mptcp-next v2 0/7] mptcp: add bpf_setsockopt support 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=f28023650f3feaec991e266ee0226c5c0110f17e.camel@kernel.org \
--to=geliang@kernel.org \
--cc=gang.yan@linux.dev \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=yangang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox