From owner-freebsd-net@freebsd.org  Sun Mar 19 18:32:06 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 304E4D13EAE
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sun, 19 Mar 2017 18:32:06 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1D51F65F
 for <freebsd-net@FreeBSD.org>; Sun, 19 Mar 2017 18:32:06 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2JIW5EL015024
 for <freebsd-net@FreeBSD.org>; Sun, 19 Mar 2017 18:32:05 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 217637] One TCP connection accepted TWO times
Date: Sun, 19 Mar 2017 18:32:06 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: tuexen@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Mar 2017 18:32:06 -0000

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.=