Re: [PATCH net-next v2 3/5] mptcp: explicitly drop over memory limits
Paolo Abeni <[email protected]> Mon, 3 Aug 2026 15:33:44 +0200
| Newsgroups | dev.linux.lists.mptcp,org.kernel.vger.linux-kernel,org.kernel.vger.netdev |
|---|---|
| Message-ID | <[email protected]> |
On 7/31/26 4:24 PM, Matthieu Baerts (NGI0) wrote: > From: Paolo Abeni <[email protected]> > > Currently the enforcement of the rcvbuf constraint is implemented > when moving the skbs into the msk receive or OoO queue, keeping the > incoming skbs in the subflow queue when over limits. > > Under significant memory pressure the above can cause permanent data > transfer stalls, as the skb needed to make forward progress can be > stuck in a subflow queue. > > Over memory limits, drop the incoming skb, relying on MPTCP-level > retransmissions. > > Note that fallback socket must perform the limit before the skb reaches > the subflow-level queue, as dropping an in-sequence already acked skb > would break the stream. > > This is not a complete fix for the stall issue, as the drop strategy > needs refinements that will come in the next patches. > > Signed-off-by: Paolo Abeni <[email protected]> > Reviewed-by: Matthieu Baerts (NGI0) <[email protected]> > [ Fix typo, comment, and bump LINUX_MIB_TCPRCVQDROP ] > Signed-off-by: Matthieu Baerts (NGI0) <[email protected]> > --- > v2: > - mib: typo: "constrains" -> "constraints". > - mptcp_over_limit: more than 0-win: retrans, dup or old acks. > - mptcp_over_limit: bump LINUX_MIB_TCPRCVQDROP. > - Note: Sashiko might point to a possible forward-allocated memory > leak: this is a temp leak, and releasing additionally allocated fwd > memory in the error path will be fix in a patch for -net. > --- > net/mptcp/mib.c | 2 ++ > net/mptcp/mib.h | 2 ++ > net/mptcp/options.c | 32 +++++++++++++++++++++++++++++--- > net/mptcp/protocol.c | 31 +++++++++++++++++++++++-------- > 4 files changed, 56 insertions(+), 11 deletions(-) > > diff --git a/net/mptcp/mib.c b/net/mptcp/mib.c > index f23fda0c55a7..ef65e2df709f 100644 > --- a/net/mptcp/mib.c > +++ b/net/mptcp/mib.c > @@ -85,6 +85,8 @@ static const struct snmp_mib mptcp_snmp_list[] = { > SNMP_MIB_ITEM("SimultConnectFallback", MPTCP_MIB_SIMULTCONNFALLBACK), > SNMP_MIB_ITEM("FallbackFailed", MPTCP_MIB_FALLBACKFAILED), > SNMP_MIB_ITEM("WinProbe", MPTCP_MIB_WINPROBE), > + SNMP_MIB_ITEM("BacklogDrop", MPTCP_MIB_BACKLOGDROP), > + SNMP_MIB_ITEM("RcvPruned", MPTCP_MIB_RCVPRUNED), > }; > > /* mptcp_mib_alloc - allocate percpu mib counters > diff --git a/net/mptcp/mib.h b/net/mptcp/mib.h > index 812218b5ed2b..9271205f682e 100644 > --- a/net/mptcp/mib.h > +++ b/net/mptcp/mib.h > @@ -88,6 +88,8 @@ enum linux_mptcp_mib_field { > MPTCP_MIB_SIMULTCONNFALLBACK, /* Simultaneous connect */ > MPTCP_MIB_FALLBACKFAILED, /* Can't fallback due to msk status */ > MPTCP_MIB_WINPROBE, /* MPTCP-level zero window probe */ > + MPTCP_MIB_BACKLOGDROP, /* Backlog over memory limit */ > + MPTCP_MIB_RCVPRUNED, /* Dropped due to memory constraints */ > __MPTCP_MIB_MAX > }; > > diff --git a/net/mptcp/options.c b/net/mptcp/options.c > index c664023d37ba..5642277c8b3d 100644 > --- a/net/mptcp/options.c > +++ b/net/mptcp/options.c > @@ -1127,8 +1127,34 @@ static bool add_addr_hmac_valid(struct mptcp_sock *msk, > return hmac == mp_opt->ahmac; > } > > -/* Return false in case of error (or subflow has been reset), > - * else return true. > +static bool mptcp_over_limit(struct sock *sk, struct sock *ssk, > + const struct sk_buff *skb) > +{ > + struct mptcp_sock *msk = mptcp_sk(sk); > + u64 mem = sk_rmem_alloc_get(sk); > + > + mem += READ_ONCE(msk->backlog_len); > + if (likely(mem <= READ_ONCE(sk->sk_rcvbuf))) > + return false; Clashiko noted this is a bit pessimistic/too strict. I *think* it can be relaxed a bit, but I'm not sure if such option would be actually better. Unfortunately this is inherently race. I will give a shot. > + /* Avoid silently dropping pure acks, fin or already-acked segments. */ > + if (TCP_SKB_CB(skb)->seq == TCP_SKB_CB(skb)->end_seq || > + TCP_SKB_CB(skb)->tcp_flags & TCPHDR_FIN || > + !after(TCP_SKB_CB(skb)->end_seq, tcp_sk(ssk)->rcv_nxt)) > + return false; > + > + /* Dropped due to memory constraints, schedule an ack. */ > + inet_csk(ssk)->icsk_ack.pending |= ICSK_ACK_NOMEM | ICSK_ACK_NOW; > + inet_csk_schedule_ack(ssk); > + > + /* Plain TCP (fallback) and skb is dropped before the TCP recv queue. */ > + NET_INC_STATS(sock_net(sk), LINUX_MIB_TCPRCVQDROP); Clashiko note this account is not correct in case of RST packet with payload; this could be a follow-up, but given the other feedback I'll give it a shot. I took the liberty to ignore minor feedback WRT comment accuracy. /P