From: "David S. Miller" <davem@davemloft.net>
To: davidel@xmailserver.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] POLLHUP tinkering ...
Date: Sun, 08 Jan 2006 16:20:17 -0800 (PST) [thread overview]
Message-ID: <20060108.162017.97708180.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0601081610130.6925@localhost.localdomain>
From: Davide Libenzi <davidel@xmailserver.org>
Date: Sun, 8 Jan 2006 16:11:10 -0800 (PST)
> On Sun, 8 Jan 2006, David S. Miller wrote:
>
> > The extra last read is always necessary, it's an error synchronization
> > barrier. Did you know that?
> >
> > If a partial read or write hits an error, the successful amount of
> > bytes read or written before the error occurred is returned. Then any
> > subsequent read or write will report the error immediately.
>
> Sorry for the missing info, but I was clearly talking about O_NONBLOCK
> here.
What I said still applies to O_NONBLOCK.
next prev parent reply other threads:[~2006-01-09 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 0:02 Davide Libenzi
2006-01-09 0:08 ` David S. Miller
2006-01-09 0:11 ` Davide Libenzi
2006-01-09 0:20 ` David S. Miller [this message]
2006-01-09 0:35 ` Davide Libenzi
2006-01-09 3:13 ` David Schwartz
2006-01-09 4:55 ` Davide Libenzi
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=20060108.162017.97708180.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®