[PATCH 4.4 137/137] tcp: do not send empty skb from tcp_write_xmit()
From: Greg Kroah-Hartman
Date: Thu Jan 02 2020 - 17:39:15 EST
From: Eric Dumazet <edumazet@xxxxxxxxxx>
[ Upstream commit 1f85e6267caca44b30c54711652b0726fadbb131 ]
Backport of commit fdfc5c8594c2 ("tcp: remove empty skb from
write queue in error cases") in linux-4.14 stable triggered
various bugs. One of them has been fixed in commit ba2ddb43f270
("tcp: Don't dequeue SYN/FIN-segments from write-queue"), but
we still have crashes in some occasions.
Root-cause is that when tcp_sendmsg() has allocated a fresh
skb and could not append a fragment before being blocked
in sk_stream_wait_memory(), tcp_write_xmit() might be called
and decide to send this fresh and empty skb.
Sending an empty packet is not only silly, it might have caused
many issues we had in the past with tp->packets_out being
out of sync.
Fixes: c65f7f00c587 ("[TCP]: Simplify SKB data portion allocation with NETIF_F_SG.")
Signed-off-by: Eric Dumazet <edumazet@xxxxxxxxxx>
Cc: Christoph Paasch <cpaasch@xxxxxxxxx>
Acked-by: Neal Cardwell <ncardwell@xxxxxxxxxx>
Cc: Jason Baron <jbaron@xxxxxxxxxx>
Acked-by: Soheil Hassas Yeganeh <soheil@xxxxxxxxxx>
Signed-off-by: Jakub Kicinski <jakub.kicinski@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
net/ipv4/tcp_output.c | 8 ++++++++
1 file changed, 8 insertions(+)
@@ -2148,6 +2148,14 @@ static bool tcp_write_xmit(struct sock *
+ /* Argh, we hit an empty skb(), presumably a thread
+ * is sleeping in sendmsg()/sk_stream_wait_memory().
+ * We do not want to send a pure-ack packet and have
+ * a strange looking rtx queue with empty packet(s).
+ if (TCP_SKB_CB(skb)->end_seq == TCP_SKB_CB(skb)->seq)
if (unlikely(tcp_transmit_skb(sk, skb, 1, gfp)))