Messages in this thread | | | Date | Wed, 17 Jul 2002 19:17:22 +0200 | From | Andries Brouwer <> | Subject | Re: close return value (was Re: [ANNOUNCE] Ext3 vs Reiserfs benchmarks) |
| |
On Tue, Jul 16, 2002 at 09:38:53PM -0700, Elladan wrote:
> The question is, does the OS standard guarantee that the fd is closed, > even if close() returns EINTR or EIO? Just going by the normal usage of > EINTR, one might think otherwise. It doesn't appear to be documented > one way or another. > > Alan said you could just issue close again to make sure - the example > shows that this is not the case. A second close is either required or > forbidden in that example - and the behavior has to be well defined or > you won't know which to do.
No, the behaviour is not well-defined at all. The standard explicitly leaves undefined what happens when close returns EINTR or EIO. - 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/
| |