From: Benjamin LaHaise <bcrl@kvack.org>
To: madanagopal <madan@nmsworks.co.in>
Cc: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Data corruption when using TCP sockets
Date: Fri, 2 Dec 2005 10:07:11 -0500 [thread overview]
Message-ID: <20051202150710.GB12152@kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0512022028230.9779@fileserver.nmsworks.co.in>
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
prev parent reply other threads:[~2005-12-02 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 11:35 Data corruption when using TCP sockets madanagopal
2005-12-02 14:26 ` Benjamin LaHaise
2005-12-02 15:01 ` madanagopal
2005-12-02 15:07 ` Benjamin LaHaise [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051202150710.GB12152@kvack.org \
--to=bcrl@kvack.org \
--cc=linux-net@vger.kernel.org \
--cc=madan@nmsworks.co.in \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).