Messages in this thread | | | Date | Thu, 15 Oct 1998 14:11:42 +0100 | From | Jamie Lokier <> | Subject | Re: ECONNREFUSED in recvfrom ? |
| |
On Tue, Oct 13, 1998 at 06:49:37PM +1300, Chris Wedgwood wrote: > It's documented, rfc1122.
The requirement to report the error is documented, but the suggested mechanism is quite unlike the Linux behaviour.
RFC1122 refers to "an upcall to the ERROR_REPORT routing (see Section 4.2.4.1)".
Later on TCP, the same upcall is suggested for reporting TCP Urgent data.
Section 4.2.4.1 is titled "Asynchronous Reports".
"Generically, we assume this takes the form of an application-supplied ERROR_REPORT routine that may be upcalled [INTRO:7] asynchronously from the transport layer."
... talk about TCP errors [it's actually a TCP-specific description, though the UDP section in RFC1122 does refer to it] ...
"However, an application program that does not want to receive such ERROR_REPORT calls SHOULD be able to effectively disable these calls."
Granted, we have SO_BSDCOMPAT.
We already have an upcall for urgent data: SIGURG and MSG_OOB. By handling SIGURG, it can be asynchronous. Shouldn't the UDP error condition be notified in a similar way?
-- Jamie
- 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/
| |