tcp: fastopen: fix rcv_wup initialization for TFO server on SYN/data
authorNeal Cardwell <ncardwell@google.com>
Tue, 30 Aug 2016 15:55:23 +0000 (11:55 -0400)
committerDavid S. Miller <davem@davemloft.net>
Thu, 1 Sep 2016 23:40:15 +0000 (16:40 -0700)
commit28b346cbc0715ae45b2814d857f1d8a7e6817ed8
tree4c9c9269d32f92058e94de57d68ed2d6dd7da10e
parent85a3d4a9356b595d5440c3f1bf07ee7cecca1567
tcp: fastopen: fix rcv_wup initialization for TFO server on SYN/data

Yuchung noticed that on the first TFO server data packet sent after
the (TFO) handshake, the server echoed the TCP timestamp value in the
SYN/data instead of the timestamp value in the final ACK of the
handshake. This problem did not happen on regular opens.

The tcp_replace_ts_recent() logic that decides whether to remember an
incoming TS value needs tp->rcv_wup to hold the latest receive
sequence number that we have ACKed (latest tp->rcv_nxt we have
ACKed). This commit fixes this issue by ensuring that a TFO server
properly updates tp->rcv_wup to match tp->rcv_nxt at the time it sends
a SYN/ACK for the SYN/data.

Reported-by: Yuchung Cheng <ycheng@google.com>
Signed-off-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: Yuchung Cheng <ycheng@google.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Soheil Hassas Yeganeh <soheil@google.com>
Fixes: 168a8f58059a ("tcp: TCP Fast Open Server - main code path")
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_fastopen.c