Re: [PATCH RFC v3] vfs: make fstatat retry once on ESTALE errors from getattr call

From: Miklos Szeredi
Date: Mon Apr 23 2012 - 10:50:47 EST

"J. Bruce Fields" <bfields@xxxxxxxxxxxx> writes:

> I also wonder whether it would be making too many assumptions about the
> server or filesystem: just because ordinary posix interfaces don't allow
> atomic replacement of a whole directory tree doesn't mean the server
> might not have some way to do it.

Exactly because posix limits the atomic replacement to empty directories
is that this feature is not useful and is why linux can get away with
the dead directory behavior in this case. And thinking about fixing
this in NFS is completely pointless since no one will rely on the atomic
replacement behavior. Fixing local filesystems is also pointless for
the same reason.

Atomic replacement of whole directory trees would indeed be more useful,
but it's highly unlikely to be used anywhere since applications relying
on this feature would be limited to special filesystems that allow this.

So my statement is "ENOENT is equivalent to ESTALE if already retrying
path lookup with LOOKUP_REVAL on any operation that takes an parent
directory and a name (lookup, create, link, unlink, symlink, mkdir,
rmdir, mknod, rename)."

This equivalence is in the sense that it doesn't change behavior
compared to local filesystems.

For other operations ENOENT is not equivalent to ESTALE.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at