> I don't think that is true. I think the directory and the file should be
> considered separate, it's just that "lookup()" can find one or the other
> depending on use..
lookup()? It will confuse the living hell of dcache lookups, for one.
> So I think it should be considered a _naming_ issue, and not much else.
Elaborate, please. What is the parent dentry of file that happens to have
the same name as a directory? What happens upon rename() over (or from)
it? I'm not asking about the implementation - just about the semantics you
want for those objects. What do you want to see if it is NFS-exported?
What do you want to have upon d_path() of such animal?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/