From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net] mptcp: fix ack generation for fallback msk
Date: Tue, 11 Nov 2025 16:30:39 +0100 [thread overview]
Message-ID: <fa8316ac-594e-443b-b9dc-00103ee8557a@kernel.org> (raw)
In-Reply-To: <14a868192851deb4145a90e3b7eec616544da262.1762474159.git.pabeni@redhat.com>
Hi Paolo,
On 07/11/2025 01:10, Paolo Abeni wrote:
> mptcp_cleanup_rbuf() need to know the last most recent, mptcp-level
> rcv_wnd sent, and such information is tracked into the msk->old_wspace
> field, updated at ack transmission time by mptcp_write_options().
>
> Fallback socket do not add any mptcp options, such helper is never
> invoked, and msk->old_wspace value remain stale. That in turn makes
> ack generation at recvmsg() time quite randomic.
>
> Address the issue ensuring mptcp_write_options() is invoked even
> for fallback sockets, and just update the needed info in such a
> case.
>
> The issue went unnoticed for a long time, as mptcp overshot the> fallback socket receive buffer autotune significantly.
Should we say "used to overshot"? :)
> Fixes: e3859603ba13 ("mptcp: better msk receive window updates")
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/594
Thank you for the fix!
(...)
> @@ -1643,6 +1660,9 @@ void mptcp_write_options(struct tcphdr *th, __be32 *ptr, struct tcp_sock *tp,
> opts->reset_transient,
> opts->reset_reason);
> return;
> + } else if (unlikely(!opts->suboptions)) {
Small detail: do you mind if I add /* Fallback to TCP */ just above when
applying the patch?
> + mptcp_track_rwin(tp);
Should we eventually also call mptcp_track_rwin(tp) in case of MP_FAIL
without MP_RST? Or is this not needed?
Other than that, it looks good to me, and I guess we can already apply
the patch:
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> + return;
> }
>
> if (OPTION_MPTCP_PRIO & opts->suboptions) {
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-11-11 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 0:10 [PATCH mptcp-net] mptcp: fix ack generation for fallback msk Paolo Abeni
2025-11-07 8:41 ` MPTCP CI
2025-11-11 9:09 ` Geliang Tang
2025-11-11 15:30 ` Matthieu Baerts [this message]
2025-11-11 15:47 ` Matthieu Baerts
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=fa8316ac-594e-443b-b9dc-00103ee8557a@kernel.org \
--to=matttbe@kernel.org \
--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