public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: gang.yan@linux.dev
To: "Paolo Abeni" <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net v3 1/2] mptcp: sync the msk->sndbuf at accept() time
Date: Sat, 11 Apr 2026 03:51:17 +0000	[thread overview]
Message-ID: <c5992c62c4e0205087c27c0ad69eef348f774bb7@linux.dev> (raw)
In-Reply-To: <9b3a7675-cf38-4107-8c79-6ec7ccdbb2e4@redhat.com>

April 10, 2026 at 5:04 PM, "Paolo Abeni" <pabeni@redhat.com mailto:pabeni@redhat.com?to=%22Paolo%20Abeni%22%20%3Cpabeni%40redhat.com%3E > wrote:


> 
> On 4/7/26 10:45 AM, Gang Yan wrote:
> 
> > 
> > From: Gang Yan <yangang@kylinos.cn>
> >  
> >  After an MPTCP connection is established, the sk_sndbuf of client's msk
> >  can be updated through 'subflow_finish_connect'. However, the newly
> >  accepted msk on the server side has a small sk_sndbuf than
> >  msk->first->sk_sndbuf:
> >  
> >  '''
> >  MPTCP: msk:00000000e55b09db, msk->sndbuf:20480, msk->first->sndbuf:2626560
> >  '''
> >  
> >  This patch synchronizes the sk_sndbuf by triggering its update during
> >  accept.
> > 
> I finally could wrap my head around the root cause: tcp_child_process()
> -> tcp_init_transfer() -> tcp_sndbuf_expand() can and will grow the ssk
> sndbuf _after_ tcp_check_req() -> subflow_syn_recv_sock() ->
> mptcp_sk_clone_init() where __mptcp_propagate_sndbuf() is currently hooked.
> 
> I think the latter __mptcp_propagate_sndbuf() invocation can be removed,
> and the commit message expanded to capture some of the above.
> 
> With the above included feel free to add:
> 
> Acked-by: Paolo Abeni <pabeni@redhat.com>
Hi Paolo,

Thanks for your suggestions. The v4 code will be sent soon.

Cherrs,
Gang
>

  parent reply	other threads:[~2026-04-11  3:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07  8:45 [PATCH mptcp-net v3 0/2] mptcp: sync the msk->sndbuf at accept() time Gang Yan
2026-04-07  8:45 ` [PATCH mptcp-net v3 1/2] " Gang Yan
2026-04-10  9:04   ` Paolo Abeni
2026-04-10  9:10     ` Matthieu Baerts
2026-04-11  3:51     ` gang.yan [this message]
2026-04-07  8:45 ` [PATCH mptcp-net v3 2/2] selftests: mptcp: add a check for sndbuf of S/C Gang Yan
2026-04-09  9:57 ` [PATCH mptcp-net v3 0/2] mptcp: sync the msk->sndbuf at accept() time 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=c5992c62c4e0205087c27c0ad69eef348f774bb7@linux.dev \
    --to=gang.yan@linux.dev \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    /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