From: Pete Zaitcev <zaitcev@redhat.com>
To: sdake@redhat.com
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: RFC loop at EOF from client socket
Date: Mon, 10 May 2010 22:49:57 -0600 [thread overview]
Message-ID: <20100510224957.568b524c@redhat.com> (raw)
In-Reply-To: <1273552822.2576.25.camel@localhost.localdomain>
On Mon, 10 May 2010 21:40:22 -0700
Steven Dake <sdake@redhat.com> wrote:
> According to Posix specifications - return from read of 0 indicates EOF;
> doesn't matter on socket options. If O_NONBLOCK is set and the read
> would block, result is -1 / errno=EAGAIN (or number of bytes read, or 0
> = EOF). There is no condition in which O_NONBLOCK should have any
> effect on read returning the value 0 to indicate an EOF.
Great, thanks for confirming this for me. This is what I assumed
for the patch, but I was afraid of rumor-based engineering.
> YMMV with BSD platforms, they have some non-compliant return values
> around poll when EOF occurs if I recall correctly.
That would be unfortunate, but we can let Jeff test it :-)
-- Pete
prev parent reply other threads:[~2010-05-11 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 4:16 RFC loop at EOF from client socket Pete Zaitcev
2010-05-11 4:40 ` Steven Dake
2010-05-11 4:49 ` Pete Zaitcev [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=20100510224957.568b524c@redhat.com \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=sdake@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).