Messages in this thread | | | Subject | Re: silent semantic changes with reiser4 | From | Trond Myklebust <> | Date | Sun, 29 Aug 2004 19:17:10 -0400 |
| |
På su , 29/08/2004 klokka 17:50, skreiv Linus Torvalds: > The general VFS layer has a lot of rules, and avoids these problems by > simply never having aliases between two directories. If the same directory > shows up multiple times (which can happen with bind mounts), they have the > exact same dentry for the directory, it's just found through two different > vfsmount instances. That's why vfsmounts exist - they allow the same name > cache entry to show up in different places at the same time.
So could you explain what is stopping us from reducing the whole problem to the bind mount problem? IOW have "a/" be a directory that acts as if it is dynamically bind mounted on top of the file "a".
Is it just the fantasy of supporting hard-links across "stream boundaries" (as in "touch a b; ln b a/b; ln a b/a")? I'm pretty sure nobody wants to have to add cyclic graph detection to their filesystems anyway. 8-)
What other issues would need to be addressed?
Cheers, Trond - 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/
| |