From owner-freebsd-net@freebsd.org Tue Mar 21 10:57:50 2017 Return-Path: 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 B6028D14B75 for ; Tue, 21 Mar 2017 10:57:50 +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 8C1951974 for ; Tue, 21 Mar 2017 10:57:50 +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 v2LAvnJk024555 for ; Tue, 21 Mar 2017 10:57:50 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: Tue, 21 Mar 2017 10:57:49 +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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 10:57:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217637 --- Comment #76 from slw@zxy.spb.ru --- (In reply to Mike Karels from comment #74) Im don't talk "TCP wait FIN", only "TCP wait ACK=3DSERVER_FIN.SEQ". Server = TCP have sending and not confirmed data, what reason to discard this server response? After got ACK=3DFIN.SEQ no objection to send RST. About incoming data to server. Is close(fd) equalent to sutdown(fd, SHUT_RD= WR)? If yes -- incoming data can acknowledged and then silently discarded: =3D=3D SHUT_RD The read half of the connection is closed=E2=80=94 No more data can be rece= ived on the socket and any data currently in the socket receive buffer is discarded. The process can no longer issue any of the read functions on the socket. Any da= ta received after this call for a TCP socket is acknowledged and then silently discarded. SHUT_WR The write half of the connection is closed=E2=80=94 In the case of TCP, thi= s is called a half-close (Section 18.5 of TCPv1). Any data currently in the socket send buffer will be sent, followed by TCP's normal connection termination sequence. As = we mentioned earlier, this closing of the write half is done regardless of whe= ther or not the socket descriptor's reference count is currently greater than 0. The process can no longer issue any of the write functions on the socket. SHUT_RDWR The read half and the write half of the connection are both closed=E2=80=94= This is equivalent to calling shutdown twice: first with SHUT_RD and then with SHUT= _WR. =3D=3D --=20 You are receiving this mail because: You are the assignee for the bug.=