On Wed, Mar 21, 2012 at 09:18:35PM +0000, Al Viro (viro@xxxxxxxxxxxxxxxxxx) wrote: > I think I've asked that question at least 3 times. Never got anything > resembling an answer... Is that misspelled dentry_path()? Or is something > subtle going on and we really want different strings generated for > chrooted processes here? This is a special case which does bad things intentionally. http-compatibility was added in _this_ POHMELFS on demand from people who do want to access files by handle created from whole path. Not name or inode number, but whole path, since that's only what is available in http (or more generally via rest api) It is limited, wrong and error-prone. It does not even support rename and hardlinks. But that's what people want. When I bind-remount part of the tree, things 'dissapear' from the tree. Yes, this is really an uglymoron, but it was created for _some_ limited case which rougly work in sandboxed environment only. The whole rest of the POHMELFS was completely rewritten with very different model, namely we do _not_ depend on pathes in general case. There are fair inodes which are indexed by 2^512 numbers, they are referenced from direntries and so forth. So, again, treat http-compat mount option (which turns this path-based-lookups) as a ugly handler for those who /skipped by censorship in editor/ know what they are doing. -- Evgeniy Polyakov -- 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
