lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 01 Apr 2016 08:44:23 -0700 From: Eric Dumazet <eric.dumazet@...il.com> To: Soheil Hassas Yeganeh <soheil.kdev@...il.com> Cc: davem@...emloft.net, netdev@...r.kernel.org, willemb@...gle.com, edumazet@...gle.com, ycheng@...gle.com, ncardwell@...gle.com, kafai@...com, Soheil Hassas Yeganeh <soheil@...gle.com> Subject: Re: [PATCH v2 net-next 2/8] tcp: accept SOF_TIMESTAMPING_OPT_ID for passive TFO On Fri, 2016-04-01 at 11:04 -0400, Soheil Hassas Yeganeh 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. Acked-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists