From: Ulrich Drepper <drepper@redhat.com>
To: netdev <netdev@vger.kernel.org>, Alan Cox <alan@redhat.com>
Subject: bind and O_NONBLOCK
Date: Thu, 20 Sep 2007 22:59:53 -0700 [thread overview]
Message-ID: <46F35DD9.4000909@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Some time back Alan asked about adding O_NONBLOCK support to bind in the
POSIX spec. I brought this up and the following text will be in the
next revision of the POSIX spec:
=======================
If the socket address cannot be assigned immediately and O_NONBLOCK is
set for the file descriptor for the socket, bind( ) shall fail and set
errno to [EINPROGRESS], but the assignment request shall not be aborted,
and the assignment shall be completed asynchronously. Subsequent calls
to bind() for the same socket, before the assignment is completed, shall
fail and set errno to [EALREADY].
When the assignment has been performed asynchronously, pselect(),
select(), and poll() shall indicate that the file descriptor for the
socket is ready for reading and writing.
=======================
It would be ideal if we'd have such an implementation in the next few
months so that we, in theory, can check whether the text in the
specification makes sense.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFG813Z2ijCOnn/RHQRAsNkAJ9EuDWX3EDez8+o/y3I39A7Axy++ACfZAXi
DRFm1UadrbJ+c7ss0a1vWUI=
=p1bV
-----END PGP SIGNATURE-----
next reply other threads:[~2007-09-21 6:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 5:59 Ulrich Drepper [this message]
2007-09-22 16:14 ` bind and O_NONBLOCK Evgeniy Polyakov
2007-09-22 16:21 ` Ulrich Drepper
2007-09-22 16:59 ` Evgeniy Polyakov
2007-09-22 17:11 ` Ulrich Drepper
2007-09-22 17:19 ` Evgeniy Polyakov
2007-09-23 5:58 ` David Miller
2007-09-23 20:43 ` Alan Cox
2007-09-22 17:35 ` Alan Cox
2007-09-22 17:40 ` Evgeniy Polyakov
2007-09-28 22:56 ` David Miller
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=46F35DD9.4000909@redhat.com \
--to=drepper@redhat.com \
--cc=alan@redhat.com \
--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).