On Mon, 17 Dec 2001, Joel Becker wrote:
> IIRC, SUS states that if a fatal error occurred causing the
> partial write, that error will be returned on the next write or upon
> close(). Thus:
>
> /* Smart program handles partial writes */
> write(100k); = 50k
> write(remaining 50k); = -1/ENOSPC|EIO|etc
We do this, if the error is "hard". And "fatal" implies hardness, so we're
ok here.
> /* Dumb program doesn't handle partial write */
> write(100k); = 50k
> close(fd); = -1/EIO
But we're not doing this.
We'd have to save the error into the "struct file" to do the close thing.
Which is what NFS actually already does for other reasons (ie the
asynchronous nature of writes and thus IO errors), so generalizing it
might actually clean some stuff up (sockets have some of the same issues,
but socket semantics may be different enough that we do not want to have
common "error on next access" handling).
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Dec 23 2001 - 21:00:14 EST