John Baldwin dbfcf8cfea When the MNTK_EXTENDED_SHARED mount option was added, some filesystems were ... changed to defer the setting of VN_LOCK_ASHARE() (which clears LK_NOSHARE in the vnode lock's flags) until after they had determined if the vnode was a FIFO. This occurs after the vnode has been inserted a VFS hash or some similar table, so it is possible for another thread to find this vnode via vget() on an i-node number and block on the vnode lock. If the lockmgr interlock (vnode interlock for vnode locks) is not held when clearing the LK_NOSHARE flag, then the lk_flags field can be clobbered. As a result the thread blocked on the vnode lock may never get woken up. Fix this by holding the vnode interlock while modifying the lock flags in this case. MFC after: 3 days		2010-07-16 19:20:20 +00:00
..
ffs	When the MNTK_EXTENDED_SHARED mount option was added, some filesystems were	2010-07-16 19:20:20 +00:00
ufs	- Handle the truncation of an inode with an effective link count of 0 in	2010-07-06 07:11:04 +00:00