Al Viro: > The trouble with such mechanisms is that they tend to end up depending on > fairly non-trivial properties of underlying fs. Try aufs one on btrfs, > see how soon you spot the problem. It's nice when a method turns out > to be really redundant and implementable in uniform way via other methods > present; see fh_to_dentry history for example of situation where it hadn't... Hmm, I could not see problem around aufs using btrfs as the upper RW branch, tested on linux-3.9-rc2. Would you describe more specifically? Some of my local tests didn't pass due to an error return from btrfs. For example, repeat "ln fileA $very_loooong_filename", then btrfs returns EMLINK so soon. And aufs refers the common set of inode attribute. I mean attrs declared in VFS. Also I know some filesystems don't maintain attrs on each operation. For such fs, aufs calls vfs_getattr() internally. J. R. Okajima -- 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
