Re: [PATCH net 4/7] mptcp: push queued data on passive TFO subflows becoming established
From: netdev-bot+sashiko
Date: Tue Nov 17 2026 - 17:30:11 EST
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] The commit message of "mptcp: push queued data on passive TFO
subflows becoming established" describes behaviour that depends on an…
--
mptcp: push queued data on passive TFO subflows becoming established
With TCP Fast Open, data written by an MPTCP server before the third ACK
could stay queued after that ACK, because the ACK carries MP_CAPABLE
without DSS, so ack_update_msk() is never called. This commit makes
check_fully_established() call __mptcp_check_push() when a subflow becomes
fully established on a passive TFO child (syn_fastopen_child), so the data
is pushed at that point.
Closes: https://lore.kernel.org/mptcp/CAFPPu1gU2Y-D+d4i3F0MoNkYK+e1U+=X3qf6QycjfKBw+8snPg@xxxxxxxxxxxxxx/
> Without this patch, and before the
> earlier commit "mptcp: arm the rtx timer if a push leaves data behind",
> this data was not sent:
>
> server-tfo-write-before-3rd-ack.pkt:24: error handling packet: Timed out waiting for packet
>
> Since this earlier commit, this data is sent, but only when the MPTCP
> retransmission timer fires, here after one second, as the tests increase
> its interval:
[Severity: Low]
Which tree is "mptcp: arm the rtx timer if a push leaves data behind" in?
That commit doesn't seem to be present here, either at this commit or at
the end of the series. The following patch, "mptcp: push queued data on
subflows falling back at the handshake", refers to it the same way. Neither
message gives a SHA or a lore link for it.
In net/mptcp/protocol.c, __mptcp_push_pending() still arms the rtx timer
only when data was copied:
net/mptcp/protocol.c:__mptcp_push_pending() {
...
/* Avoid scheduling the rtx timer if no data has been pushed; the timer
* will be updated on positive acks by __mptcp_cleanup_una().
*/
if (copied) {
if (!mptcp_rtx_timer_pending(sk))
mptcp_reset_rtx_timer(sk);
mptcp_check_send_data_fin(sk);
}
}
__mptcp_subflow_push_pending() also arms it only inside its if (copied)
block.
So in this tree, without this patch, the data would hit the "Timed out
waiting for packet" case. It would not be sent late, after the one second
delay.
Could the changelog say where that commit lives, for example with a SHA or
a lore link? That would let stable backporters find the dependency and see
how the two changes are ordered.
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261116-net-mptcp-misc-fixes-7-4-rc4-v1-0-bf7656de653e%40kernel.org