From: "David N. Lombard" <david.lombard@mscsoftware.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] s_maxbytes handling
Date: Tue, 22 May 2001 11:24:45 -0700 [thread overview]
Message-ID: <3B0AAEED.ED8A115F@mscsoftware.com> (raw)
In-Reply-To: <3B0A7C0F.C824FDB5@uow.edu.au> <E152Dik-00021y-00@the-village.bc.nu> <9ee8qo$jgk$1@penguin.transmeta.com>
Linus Torvalds wrote:
>
[deletia]
>
> So returning 0 for write() is usually a bad idea - exactly because it
> does not have very well-defined semantics. So -EFBIG is certainly the
> preferable return value, and seems to be what SuS wants, too.
And what LFS wants too:
2.2.1.27 write() and writev()
DESCRIPTION
For regular files, no data transfer will occur past the offset
maximum established in the open file description associated with
fildes.
ERRORS
These functions will fail if:
[EFBIG]
The file is a regular file, nbyte is greater than 0 and the
starting position is greater than or equal to the offset
maximum established in the open file description associated
with fildes.
Note: This is an additional EFBIG error condition.
--
David N. Lombard
next prev parent reply other threads:[~2001-05-22 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 12:52 [patch] s_maxbytes handling Andrew Morton
2001-05-22 13:27 ` Alan Cox
2001-05-22 14:47 ` Andrew Morton
2001-05-22 15:05 ` Alan Cox
2001-05-22 17:49 ` Linus Torvalds
2001-05-22 18:24 ` David N. Lombard [this message]
2001-05-23 18:02 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2001-05-22 19:33 Andries.Brouwer
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=3B0AAEED.ED8A115F@mscsoftware.com \
--to=david.lombard@mscsoftware.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.