working with vn_fullpath
Hiten Pandya
hmp at backplane.com
Mon Jun 28 03:42:45 PDT 2004
Andrew Sporner wrote:
Hiten Pandya wrote:
Basically, the one rule to keep in mind is that the vn_fullpath
can only construct a pathname if *all* its namecache components
are available, otherwise it returns ENOENT, naturally meaning
it can't find one of the components.
I have checked the code out. It is resembling my usage.
Therefore it most be as you describe about missing components.
OK. You can probably do a lookup for all the components.
What I don't understand yet, is that why would you like to
have the namecache components when doing something like
journalling?
Since we really can't afford to miss filesystem events for such
things like journaling; this is most likely not the way to achieve
what I wanted and the workarounds that I did probably need to
be upgraded in their status.
Hope that answers your queries; otherwise, please do not
hesitate to ask more questions if any! :-)
Many thanks for your feedback. This was my first post here and
to get a reply in such short order is quite remarkable.
No problem. As I said, do not hesitate to ask more questions!
Regards,
-Hiten
hmp at xxxxxxxxxxxxx
More information about the Kernel
mailing list