Messages in this thread | | | Subject | Re: [ANNOUNCE] Ext3 vs Reiserfs benchmarks | From | Alan Cox <> | Date | 15 Jul 2002 23:55:12 +0100 |
| |
On Mon, 2002-07-15 at 21:55, Matthias Andree wrote: > I assume that most will just call close() or fclose() and exit() right > away. Does fclose() imply fsync()?
It doesn't.
> Some applications will not even check the [f]close() return value...
We are only interested in reliable code. Anything else is already fatally broken.
-- quote -- Not checking the return value of close is a common but nevertheless serious programming error. File system implementations which use techniques as ``write-behind'' to increase performance may lead to write(2) succeeding, although the data has not been written yet. The error status may be reported at a later write operation, but it is guaranteed to be reported on closing the file. Not checking the return value when closing the file may lead to silent loss of data. This can especially be observed with NFS and disk quotas.
- 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/
| |