[Vortex] async connect issue on linux 2.4
Francis Brosnan Blazquez
francis at aspl.es
Mon Oct 20 15:23:40 CEST 2008
> found an issue in asyncronous connecting in __vortex_connection_new:
> i couldn't figure out why, but it seems that - at least on linux 2.4
> and older
> glibc versions - the select/poll after a non-blocking connect may (in
> rare cases!) result a value >0 though the connection wasn't
> established at
> i think it has something to do with the arp handling in the kernel,
> but i'm
> not sure.
> anyway, querying the SO_ERROR option on the socket results an error in
> case and one can find out that the connection is not established.
> appended tiny patch queries that option in the
> function, and it works for me.
Ok. The patch looks ok Martin (even having no way to reproduce the
problem). Your patch flags "these errors" as fatal. Is is this right?
I mean, when the error happens you know the remote peer is not accesible
(even waiting for the timeout).
Please confirm me this point to apply the patch. Thanks Martin!
> martin huter
Francis Brosnan Blazquez <francis at aspl.es>
Advanced Software Production Line, S.L.
More information about the Vortex