Re: 2.2.14 TCP close problem - race?

From: Alan Cox (
Date: Wed May 24 2000 - 09:59:30 EST

> The client establishes a session, sends a request and receives ECONNRESET
> instead of the data expected. The server side reports no errors. It

That sounds reasonable

> My uneducated guess is a race of some sort in the TCP close routine
> where the closed state is being marked prematurely before all data is
> sent and acked.

The application is closing the socket with data sent by the client as
yet unread. The TCP specifications require this causes a reset so the client
knows the data is lost. Probably the server needs fixing - perhaps its not
reading the last \n or something ?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:11 EST