Subject: Re: UBC info
To: Chuck Silvers <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 06/16/1999 10:48:20
On Tue, 15 Jun 1999 21:09:35 -0700
Chuck Silvers <firstname.lastname@example.org> wrote:
> I was planning on just letting i/o errors return EFAULT to the application.
> I can't think of an application that would really care whether a read()
> failed because of bogus arguments vs. an i/o error. either way, the data
> doesn't get where it was supposed to go.
It might affect the error recovery of the program. If an I/O error occurs,
you really ought to return EIO.
> does anyone feel it's important to retain EIO returns for real i/o errors
> in the filesystem? there's a performance benefit for letting them turn
> into EFAULT (or so the theory goes).
See above :-)
-- Jason R. Thorpe <email@example.com>