From owner-freebsd-net@freebsd.org  Mon Mar 20 16:54:33 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 60B6AD13537
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Mon, 20 Mar 2017 16:54:33 +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 50B04E4B
 for <freebsd-net@FreeBSD.org>; Mon, 20 Mar 2017 16:54:33 +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 v2KGsWWV040065
 for <freebsd-net@FreeBSD.org>; Mon, 20 Mar 2017 16:54:33 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: Mon, 20 Mar 2017 16:54:33 +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: slw@zxy.spb.ru
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-B1L74Ss1BZ@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: Mon, 20 Mar 2017 16:54:33 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637

--- Comment #65 from slw@zxy.spb.ru ---
(In reply to Michael Tuexen from comment #64)

> No. The server sends a RST and move the connection to CLOSED. The connect=
ion is
> terminated immediately from the server perspective.

This is wrong behaviour. This is cause lost of server data.

> No. This is an ungraceful termination. No need to wait for anything. All =
peers
> should handle the RST.

No.

pwrite();
close();

This is graceful termination.

> No. Incoming user data is lost on the server side. I think the server sho=
uld
notify
> the peer as soon as possible. Please note that the RST is only sent if the
server
> has to drop user data. If that is not the case, a graceful shutdown will =
be
performed.

User data is second question for server. Main question is resend server res=
pond
to client. This is RFC requiriment. And this is more impotant for user -- s=
ee
respond from server, not just droped connection.

Server can send RST after client ACK server respose and server FIN.

--=20
You are receiving this mail because:
You are the assignee for the bug.=