tcp: fastopen: avoid negative sk_forward_alloc
When DATA and/or FIN are carried in a SYN/ACK message or SYN message, we append an skb in socket receive queue, but we forget to call sk_forced_mem_schedule(). Effect is that the socket has a negative sk->sk_forward_alloc as long as the message is not read by the application. Josh Hunt fixed a similar issue in commitd22e153718
("tcp: fix tcp fin memory accounting") Fixes:168a8f5805
("tcp: TCP Fast Open Server - main code path") Signed-off-by: Eric Dumazet <edumazet@google.com> Reviewed-by: Josh Hunt <johunt@akamai.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
40e3012e6e
commit
76061f631c
|
@ -150,6 +150,7 @@ void tcp_fastopen_add_skb(struct sock *sk, struct sk_buff *skb)
|
|||
tp->segs_in = 0;
|
||||
tcp_segs_in(tp, skb);
|
||||
__skb_pull(skb, tcp_hdrlen(skb));
|
||||
sk_forced_mem_schedule(sk, skb->truesize);
|
||||
skb_set_owner_r(skb, sk);
|
||||
|
||||
TCP_SKB_CB(skb)->seq++;
|
||||
|
|
Loading…
Reference in New Issue