Jeff Roberson ce1fb23146 - Remove interlock protection around VI_XLOCK. The interlock is not ... sufficient to guarantee that this race is not hit. The XLOCK will likely have to be redesigned due to the way reference counting and mutexes work in FreeBSD. We currently can not be guaranteed that xlock was not set and cleared while we were blocked on the interlock while waiting to check for XLOCK. This would lead us to reference a vnode which was not the vnode we requested. - Add a backtrace() call inside of INVARIANTS in the hopes of finding out if this condition is ever hit. It should not, since we should be retaining a reference to the vnode in these cases. The reference would be sufficient to block recycling.		2003-09-19 23:37:49 +00:00
..
nwfs_io.c	- Remove interlock protection around VI_XLOCK. The interlock is not	2003-09-19 23:37:49 +00:00
nwfs_ioctl.c
nwfs_mount.h
nwfs_node.c
nwfs_node.h
nwfs_subr.c
nwfs_subr.h
nwfs_vfsops.c
nwfs_vnops.c	Add the same KASSERT to all VOP_STRATEGY and VOP_SPECSTRATEGY implementations	2003-06-15 18:53:00 +00:00
nwfs.h