Re: [PATCH net-next 2/8] tcp: accept SOF_TIMESTAMPING_OPT_ID for passive TFO
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: 2016-03-31 03:36:21
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: 2016-03-31 03:36:21
On Wed, Mar 30, 2016 at 6:37 PM, Soheil Hassas Yeganeh [off-list ref] wrote:
From: Soheil Hassas Yeganeh <redacted> SOF_TIMESTAMPING_OPT_ID is set to get data-independent IDs to associate timestamps with send calls. For TCP connections, tp->snd_una is used as the starting point to calculate relative IDs. This socket option will fail if set before the handshake on a passive TCP fast open connection with data in SYN or SYN/ACK, since setsockopt requires the connection to be in the ESTABLISHED state. To address these, instead of limiting the option to the ESTABLISHED state, accept the SOF_TIMESTAMPING_OPT_ID option as long as the connection is not in LISTEN or CLOSE states. Signed-off-by: Soheil Hassas Yeganeh <redacted>
Acked-by: Willem de Bruijn <willemb@google.com>