From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: Data corruption when using TCP sockets
Date: Fri, 2 Dec 2005 10:07:11 -0500
Message-ID: <20051202150710.GB12152@kvack.org>
References: <Pine.LNX.4.58.0512021638130.3304@fileserver.nmsworks.co.in> <20051202142625.GA12152@kvack.org> <Pine.LNX.4.58.0512022028230.9779@fileserver.nmsworks.co.in>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-net@vger.kernel.org, netdev@vger.kernel.org
Return-path: <linux-net-owner@vger.kernel.org>
To: madanagopal <madan@nmsworks.co.in>
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.58.0512022028230.9779@fileserver.nmsworks.co.in>
Sender: linux-net-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

On Fri, Dec 02, 2005 at 08:31:01PM +0530, madanagopal wrote:
> hai,
>    Sorry to ask again. Was this exact problem noticed and fixed in some 
> kernel version? If so which version is it? If it is not possible to get 
> that info, which version should we use and are we guaranteed that this 
> problem will not be present in it?

It certainly isn't a known problem with any recent 2.4 or 2.6 kernels.

		-ben