Date: Mon, 20 Mar 2017 21:40:27 +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-IB4z7MRrbC@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 #72 from Michael Tuexen <tuexen@freebsd.org> --- (In reply to slw from comment #71) I'm not arguing the semantic of the TCP level ACKs. I'm saying that if a TCP stack knows that some user data can not be deliver= ed to its application, it should signal that to the peer. This includes: * receiving data after the socket was closed or shutdown(..., SHUT_RD) was called. * closing the socket or calling shutdown(..., SHUT_RD) with user data still= in the receive buffer. I think: * these four cases should be handled the same way. * Resetting the TCP connection is what I would expect. I can write some packetdrill test scripts to see what the current behaviour= is under FreeBSD (and Linux). --=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-IB4z7MRrbC>