Re: 2.2.14 TCP close problem - race?

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Wed May 24 2000 - 10:59:30 EDT

Next message: Markus Pfeiffer: "Re: Kernel 2.4 delay ..."

Previous message: Alan Cox: "Re: [PATCH] bttv driver II"
In reply to: Charlie Brady: "2.2.14 TCP close problem - race?"
Next in thread: I-Ming Chen: "Re: 2.2.14 TCP close problem - race?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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 ?

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Markus Pfeiffer: "Re: Kernel 2.4 delay ..."
Previous message: Alan Cox: "Re: [PATCH] bttv driver II"
In reply to: Charlie Brady: "2.2.14 TCP close problem - race?"
Next in thread: I-Ming Chen: "Re: 2.2.14 TCP close problem - race?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed May 24 2000 - 11:18:20 EDT