simplifying linux_emul_convpath()  Don Lewis truckman at Wed Jan
14 13:02:12 PST 2004  On 14 Jan, Robert Watson wrote: > On Wed,
14 Jan 2004, Don Lewis wrote: >> I just stumbled across a vnode
locking violation in >> linux_emul_convpath().  Rather than
locking and unlocking each vnode for >> the VOP_GETATTR() calls,
is there any reason that this code should not >> be simplified
to just compare the vnode pointers rather than fetching >> the
vnode attributes and comparing the attributes for equality.  >
For some time, I've been thinking of adding samefile() and
fsamefile()  > system calls to FreeBSD, which would allow
userspace applications to > determine if two names or file
handles refer to the same object without > playing games with
inode numbers, device ids, etc.  The reason to do this > would
be that 32-bit inode numbers are subject to collision on large
file > systems.  My initial implementation simply compared vnode
pointers, but > that raises an interesting question about how
stacked file systems shoul