From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752138AbcGAQHd (ORCPT ); Fri, 1 Jul 2016 12:07:33 -0400 Received: from lxorguk.ukuu.org.uk ([81.2.110.251]:52978 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750715AbcGAQHb (ORCPT ); Fri, 1 Jul 2016 12:07:31 -0400 Date: Fri, 1 Jul 2016 17:04:41 +0100 From: One Thousand Gnomes To: Jason Baron Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, davem@davemloft.net, eric.dumazet@gmail.com Subject: Re: strange Mac OSX RST behavior Message-ID: <20160701170441.51d21d48@lxorguk.ukuu.org.uk> In-Reply-To: <1467385815-6357-1-git-send-email-jbaron@akamai.com> References: <1467385815-6357-1-git-send-email-jbaron@akamai.com> Organization: Intel Corporation X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Mac OSX 10.11.5 (latest version), we have found that when tcp > connections are abruptly terminated (via ^C), a FIN is sent followed > by an RST packet. The RST is sent with the same sequence number as the > FIN, and thus dropped since the stack only accepts RST packets matching > rcv_nxt (RFC 5961). The Linux behaviour appears to be correct, and accepting a broken FIN is most definitely a bad idea, it has a very different effect to a FIN because there can be data going the other direction and a FIN is a one way close Alan