Re: What happened to my /proc/curproc/file?

2012-09-04 Thread Sam Varshavchik
John Baldwin writes: On Tuesday, September 04, 2012 7:10:42 am Sam Varshavchik wrote: > Konstantin Belousov writes: > > > The procfs links, as well as any other user of vn_fullpath(9) function, > > can only translate a vnode to path if namecache contains useful data. > >

Re: What happened to my /proc/curproc/file?

2012-09-04 Thread Sam Varshavchik
Konstantin Belousov writes: The procfs links, as well as any other user of vn_fullpath(9) function, can only translate a vnode to path if namecache contains useful data. As such, the facilities are not guaranteed to success all the time. In case of rmdir(2), UFS explicitely purges the cache for

What happened to my /proc/curproc/file?

2012-09-03 Thread Sam Varshavchik
Am I the only one who's seeing this weirdness with procfs on 9.0-RELEASE-p3. Unless I'm overlooking something stupid, a process that rmdir(2)s a subdirectory of its current directory ends up with a broken /proc/curproc/file symlink: [mrsam@freebsd ~/stasher/stasher]$ cat t.c #include #incl