Re: read/recv sometimes returns EAGAIN instead of EINTR on SMPmachines

• Next message: Abraham vd Merwe: "Fwd: [allen@ct.spi.co.za: Re: [CLUG-tech] statfs() vs. df]"
• Previous message: Christian Neumair: "Re: Separate 2.4 and 2.5 lkml?"
• In reply to: David S. Miller: "Re: read/recv sometimes returns EAGAIN instead of EINTR on SMP machines"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"David S. Miller" wrote:

> Can you cite some part of the POSIX spec which states that EAGAIN
> cannot be returned when signals are received by a caller of
> tcp_recvmsg?

See: http://www.opengroup.org/onlinepubs/007904975/functions/recv.html

IMHO, the text is in no way unclear that EAGAIN is not the correct return
code for the situation while EINTR definitely is.

Regards,

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

• Next message: Abraham vd Merwe: "Fwd: [allen@ct.spi.co.za: Re: [CLUG-tech] statfs() vs. df]"
• Previous message: Christian Neumair: "Re: Separate 2.4 and 2.5 lkml?"
• In reply to: David S. Miller: "Re: read/recv sometimes returns EAGAIN instead of EINTR on SMP machines"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jul 23 2002 - 22:00:42 EST