jeff 1968343329 - Since rev 1.142 of ffs_snapshot.c the interlock has not been required ... to protect the v_lock pointer. Removing the interlock acquisition here allows vn_lock() to proceed without requiring the interlock at all. - If the lock mutated while we were sleeping on it the interlock has been dropped. It is conceivable that the upper layer code was relying on the interlock and LK_NOWAIT to protect the identity or state of the vnode while acquiring the lock. In this case return EBUSY rather than trying the new lock to prevent potential races. Reviewed by: tegge		2008-03-31 07:55:45 +00:00
..
ffs	- Since rev 1.142 of ffs_snapshot.c the interlock has not been required	2008-03-31 07:55:45 +00:00
ufs	Add the new kernel-mode NFS Lock Manager. To use it instead of the	2008-03-26 15:23:12 +00:00