Date: Sun, 19 Mar 2017 18:32:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217637] One TCP connection accepted TWO times Message-ID: <bug-217637-2472-odRCwMlGz3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217637-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-217637-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637 --- Comment #35 from Michael Tuexen <tuexen@freebsd.org> --- (In reply to slw from comment #34) > I am don't understund this. CLOSING must be only after got FIN. > FIN don't received, data in buffer don't ack, what reasson to CLOSING tra= nsition > and lost data? I haven't said that the state CLOSING is ever used. Not sure why you bring = this up... > I mean resend response and FIN again. This doesn't happen because NEW data arrives and the application has called close(). So this new data cannot be delivered to the application. The TCP stack has = do drop it. That is why a RST is sent and the connection is moved to CLOSED. I"m not sure which text you are citing, but are you trying to argue that a = TCP stack should drop data and not signal this to the other side? Just letting = the peer think everything is fine? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217637-2472-odRCwMlGz3>