From: Erik Mouw <mouw@nl.linux.org>
To: Saquib Imam <saquib.imam@patni.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: In which case EWOULDBLOCK is set while a write operation
Date: Wed, 19 Dec 2007 18:13:26 +0100 [thread overview]
Message-ID: <20071219171326.GC15327@gateway.home> (raw)
In-Reply-To: <200712180553.lBI5rQgD004427@arlmail.patni.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
On Tue, Dec 18, 2007 at 11:27:49AM +0530, Saquib Imam wrote:
> In which case EWOULDBLOCK / EAGAIN is set while a write operation ?
From write(2):
ERRORS
EAGAIN Non-blocking I/O has been selected using O_NONBLOCK and the
write would block.
Erik
--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-12-19 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 5:57 In which case EWOULDBLOCK is set while a write operation Saquib Imam
2007-12-18 12:46 ` Mulyadi Santosa
2007-12-19 17:13 ` Erik Mouw [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=20071219171326.GC15327@gateway.home \
--to=mouw@nl.linux.org \
--cc=linux-scsi@vger.kernel.org \
--cc=saquib.imam@patni.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