From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S932507AbZICXXM@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932507AbZICXXM (ORCPT <rfc822;w@1wt.eu>);
	Thu, 3 Sep 2009 19:23:12 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756559AbZICXXL
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 3 Sep 2009 19:23:11 -0400
Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:34094
	"EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1756548AbZICXXK (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 3 Sep 2009 19:23:10 -0400
Date: Thu, 03 Sep 2009 16:23:25 -0700 (PDT)
Message-Id: <20090903.162325.64855258.davem@davemloft.net>
To: treker.chen@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why sometimes linux kernel does not reply the ACK of second
 FIN packet?
From: David Miller <davem@davemloft.net>
In-Reply-To: <8e8a9c7c0909030741j63a26192m54feab96cc9fbd5a@mail.gmail.com>
References: <8e8a9c7c0909030737g7ca5746at4bf51940ff690b36@mail.gmail.com>
	<8e8a9c7c0909030741j63a26192m54feab96cc9fbd5a@mail.gmail.com>
X-Mailer: Mew version 6.2.51 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


You're more likely to get a response on the networking developer
list (netdev@vger.kernel.org), than here.