[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK6E8=erHhYPz8+H+GQ7WGrU1OSua4ZvjDKA+U6LzoCp7=YJYA@mail.gmail.com>
Date: Thu, 31 Mar 2016 16:43:22 -0700
From: Yuchung Cheng <ycheng@...gle.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc: Soheil Hassas Yeganeh <soheil.kdev@...il.com>,
David Miller <davem@...emloft.net>,
Network Development <netdev@...r.kernel.org>,
Willem de Bruijn <willemb@...gle.com>,
Eric Dumazet <edumazet@...gle.com>,
Neal Cardwell <ncardwell@...gle.com>,
Martin KaFai Lau <kafai@...com>,
Soheil Hassas Yeganeh <soheil@...gle.com>
Subject: Re: [PATCH net-next 2/8] tcp: accept SOF_TIMESTAMPING_OPT_ID for
passive TFO
On Wed, Mar 30, 2016 at 8:35 PM, Willem de Bruijn
<willemdebruijn.kernel@...il.com> wrote:
> On Wed, Mar 30, 2016 at 6:37 PM, Soheil Hassas Yeganeh
> <soheil.kdev@...il.com> wrote:
>> From: Soheil Hassas Yeganeh <soheil@...gle.com>
>>
>> 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 <soheil@...gle.com>
>
> Acked-by: Willem de Bruijn <willemb@...gle.com>
Acked-by: Yuchung Cheng <ycheng@...gle.com>
Powered by blists - more mailing lists