Hi guys,
On Tue, Mar 04, 2014 at 12:30:18AM +0100, Lukas Tribus wrote:
> Hi Joshua,
>
>
> > Hi folks,
> >
> > I was testing haproxy-1.5-dev22 on SmartOS (an illumos-based system)
> > and ran into a problem. There's a small window after non-blocking
> > connect() is called, but before the TCP connection is established,
> > where recv() may return ENOTCONN. On Linux, the behaviour here seems
> > to be always to return EAGAIN. The fix is relatively trivial, and
> > appears to make haproxy work reliably on current SmartOS (see patch
> > below). It's possible that other UNIX platforms exhibit this
> > behaviour as well.
> >
> > Does this fix appear to be acceptable?
>
> The same thing was already done for send() in commit 0ea0cf606e1d ("BUG:
> raw_sock: also consider ENOTCONN in addition to EAGAIN") [1].
>
> CC'ing Willy.
Good point. I've amended the commit message, applied it and tagged it
for backport to 1.4 as well.
Thanks!
willy
