> When the real superblock is created. It could even be the _same_ > super block as the real one. There'd be just the problem of anchoring > the dir-on-file dentries somewhere... > > Or with fuse the dir-on-file mount can just come from any mounted > filesystem, again possibly the same one as the parent. I do actually > test with this. The userspace filesystem supplies a file descriptor, > from which the struct path is extracted and returned from ->enter(). Then I do not understand what this mechanism could be used for, other than an odd way to twist POSIX behaviour and see how much of the userland would survive that. Certainly not useful for your "look into tarball as a tree", unless you seriously want to scan the entire damn fs for tarballs at mount time and set up a superblock for each. And for per-file extended attributes/forks/whatever-you-call-that-abomination it also obviously doesn't help, since you lose them for directories. IOW, what uses do you have in mind? Complete scenario, please... - 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
