--nextPart1667467.pKlgER0ZW3
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Monday, 31. January 2005 18:01, Joerg Sonnenberger wrote:
> > Yes, generating a path from a namecache pointer is triival. Just
> > recurse up through the parent pointers and pull out the segment nam=
es
> > from the namecache structures encountered, with one or two special
> > cases when crossing mount points. So in your patch set you can tell
> > nlookup_init() to get the path directly from user space and not copy it
> > anywhere.
> OK, sounds good. I'll split vn_fullpath and use that. pr_path can go away.
> I can depend on the namecache entry staying?
i guess if you keep it referenced, yes...
cheers
simon
=2D-=20
/"\
\ /
\ ASCII Ribbon Campaign
/ \ Against HTML Mail and News
--nextPart1667467.pKlgER0ZW3
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQBB/mXlr5S+dk6z85oRAplnAKDDf5liwJllJe4qi0NrieUf/AYD9QCdE+KS
6VSf5NPGxntbtLYAi977C4E=
=ksuH
-----END PGP SIGNATURE-----
--nextPart1667467.pKlgER0ZW3--