Hi,
On Wed, 2005-04-06 at 11:01, Hifumi Hisashi wrote:
> >Certainly it's normal for a short read/write to imply either error or
> >EOF, without the error necessarily needing to be returned explicitly.
> >I'm not convinced that the Singleunix language actually requires that,
> >but it seems the most obvious and consistent behaviour.
> When an O_SYNC flag is set , if commit_write() succeed but
> generic_osync_inode() return
> error due to I/O failure, write() must fail .
Yes. But it is conventional to interpret a short write as being a
failure. Returning less bytes than were requested in the write
indicates that the rest failed. It just doesn't give the exact nature
of the failure (EIO vs ENOSPC etc.) For regular files, a short write is
never permitted unless there are errors of some description.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
