From: Michael Shuldman <michaels@inet.no>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
karls@inet.no, netdev <netdev@vger.kernel.org>
Subject: Re: bug in select(2) regarding non-blocking connect(2) completion?
Date: Sat, 7 May 2011 18:06:28 +0200 [thread overview]
Message-ID: <20110507160628.GA11163@jensen.inet.no> (raw)
In-Reply-To: <1304770358.2821.1139.camel@edumazet-laptop>
Eric Dumazet wrote,
> Well, if you missed the original error report, all next getpeername()
> and SO_ERROR will do the same, and select() says fd is ready for 'write'
Many thanks for that. I was not aware that SO_ERROR would not get
set if the connect(2) failed "permanently" immediately, but have
now tested that it does. The other "strangeness" might very well
be caused by bugs related to this, so apologies for the noise and
many thanks for the help.
With kind regards,
--
_ //
\X/ -- Michael Shuldman
prev parent reply other threads:[~2011-05-07 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110507105152.GA13459@jensen.inet.no>
2011-05-07 12:12 ` bug in select(2) regarding non-blocking connect(2) completion? Eric Dumazet
2011-05-07 16:06 ` Michael Shuldman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110507160628.GA11163@jensen.inet.no \
--to=michaels@inet.no \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=karls@inet.no \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).