tcp: do not set snd_ssthresh in tcp_create_openreq_child()
authorEric Dumazet <edumazet@google.com>
Thu, 17 Jan 2019 19:23:32 +0000 (11:23 -0800)
committerDavid S. Miller <davem@davemloft.net>
Fri, 18 Jan 2019 06:19:04 +0000 (22:19 -0800)
New sockets get the field set to TCP_INFINITE_SSTHRESH in tcp_init_sock()
In case a socket had this field changed and transitions to TCP_LISTEN
state, tcp_disconnect() also makes sure snd_ssthresh is set to
TCP_INFINITE_SSTHRESH.

So a listener has this field set to TCP_INFINITE_SSTHRESH already.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_minisocks.c

index 12affb7864d981a6494059232c4965aaee756803..0cffa5937b1261984c3986b107220af495264437 100644 (file)
@@ -488,7 +488,6 @@ struct sock *tcp_create_openreq_child(const struct sock *sk,
        newtp->packets_out = 0;
        newtp->retrans_out = 0;
        newtp->sacked_out = 0;
-       newtp->snd_ssthresh = TCP_INFINITE_SSTHRESH;
        newtp->tlp_high_seq = 0;
        newtp->lsndtime = tcp_jiffies32;
        newsk->sk_txhash = treq->txhash;