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 09:26:25 -0500 [thread overview]
Message-ID: <20051202142625.GA12152@kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0512021638130.3304@fileserver.nmsworks.co.in>
That kernel is beyond ancient -- a 2.4.9 errata kernel was released on
the day that Red Hat 7.2 shipped. It is known buggy and superceeded by
many kernels with substantial bugfixes.
-ben
On Fri, Dec 02, 2005 at 05:05:28PM +0530, madanagopal wrote:
> hai,
> We have a socket application in C which connects to a Java application
> through TCP sockets. We use read() system call to read from the socket.
> The Java application sends more than 20000 bytes of data sometimes. In the
> C program, we read those bytes as Type,Length,Value fields where a
> separate read() call is used for each field. This sometimes creates a data
> corruption while it works other times.
> We observe that the first 16384 bytes get read properly. Extra byte or
> bytes get added in the 16385 th location and this shifts the bytes from
> 16385 onwards. Because of this our C program gets confused and we are
> forced to reopen the socket. This is not predictable. Suddenly this
> problem occurs. Is this an already known issue and if so what
> is it? How to solve it?
> We are running both the applications in the same machine which runs
> Red Hat Linux release 7.2 and its kernel version is 2.4.7-10
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
"You know, I've seen some crystals do some pretty trippy shit, man."
Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2005-12-02 14:26 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 [this message]
2005-12-02 15:01 ` madanagopal
2005-12-02 15:07 ` Benjamin LaHaise
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=20051202142625.GA12152@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).