> I don't know why it is hard or inefficient to implement this at the VFS
> level, though I'm sure there is a reason or this thread wouldn't
> exist. Stephen, perhaps you could explain for the record why sys_fsync
> can't just walk the chain of dentry parent links doing fdatasync? Does
> this create VFS or Ext3 locking problems? Or maybe it repeats work
> that Ext3 is already supposed to have done?
Parent directory can be renamed. Which grandparent should we sync?
New one? Old one? Both? BTW, how about file itself getting renamed during
fsync()?
See the problem? And no, blocking all renames while fsync() happens is
not an answer - it's a DoS.
> [1] In Ext2, all filename dirents are "hard links", i.e., there is no
> way to tell which of the two names is the original after creating a new
> hard link.
s/Ext2/UNIX/.
-
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/