From 9489a8e21b05852697c1ba0cb2f1eb5b712ab5d6 Mon Sep 17 00:00:00 2001 From: wollman Date: Fri, 26 Aug 1994 22:27:16 +0000 Subject: Obey RFC 793, section 3.4: Several examples of connection initiation follow. Although these examples do not show connection synchronization using data-carrying segments, this is perfectly legitimate, so long as the receiving TCP doesn't deliver the data to the user until it is clear the data is valid (i.e., the data must be buffered at the receiver until the connection reaches the ESTABLISHED state). --- sys/netinet/tcp_reass.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sys/netinet/tcp_reass.c') diff --git a/sys/netinet/tcp_reass.c b/sys/netinet/tcp_reass.c index 674b7d9..68fc751 100644 --- a/sys/netinet/tcp_reass.c +++ b/sys/netinet/tcp_reass.c @@ -31,7 +31,7 @@ * SUCH DAMAGE. * * @(#)tcp_input.c 8.5 (Berkeley) 4/10/94 - * $Id: tcp_input.c,v 1.5 1994/08/02 07:49:01 davidg Exp $ + * $Id: tcp_input.c,v 1.6 1994/08/18 22:35:32 wollman Exp $ */ #ifndef TUBA_INCLUDE @@ -182,7 +182,7 @@ present: * Present data to user, advancing rcv_nxt through * completed sequence space. */ - if (TCPS_HAVERCVDSYN(tp->t_state) == 0) + if (TCPS_HAVEESTABLISHED(tp->t_state) == 0) return (0); ti = tp->seg_next; if (ti == (struct tcpiphdr *)tp || ti->ti_seq != tp->rcv_nxt) -- cgit v1.1