On Tue, Jul 26, 2011 at 11:59 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
>
> In addition to beeing bogus the code also is useless. fsync on a file
> explicitly does not guarantee anything at all about the parent, and
> never really has on Linux either.
Well, it may never have done that, but it might still be a case of
quality-of-implementation.
The data blocks and inode indirect blocks being stable on disk doesn't
help hugely if you cannnot actually reach the inode itself.
But yeah, I suspect it's not worth the bother. For many common
situations, it's the rename that moves it to the final place that is
the critical one as far as parent directory is concerned, not the
fsync of the file itself.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
