complicated. it only looks the name up once in the underlying filesystem
and then caches the vnode reference. this area is ugly and is probably
a mistake - i think it would be better to re-do the lookup each time and
keep track of the pathname tail (with all that entails) in the union vnode.
only directory paths need to be tracked, so hard links are not an issue.
jan-simon.
Alexander Viro wrote:
> ObUnrelated: last time when I looked into your code in sys/miscfs/unionfs
> was _long_ ago and I'm trying to recall how it handles directory renames
> on the covered filesystem. I _never_ tried to do that (not even sure that
> one can mount unionfs with underlying fs mounted r/w and accessible), but
> ISTR that there were problems. And it looks like we may need something
> of that kind. Could you comment on the potential nasties that may lurk
> there?
> Cheers,
> Al
>
-
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/
This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:16 EST