summaryrefslogtreecommitdiffstats
path: root/sys/ufs
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2010-07-16 19:20:20 +0000
committerjhb <jhb@FreeBSD.org>2010-07-16 19:20:20 +0000
commitea417bf09acdf5d9f44a16d4325b3b99dda501e3 (patch)
tree9b1c6ddf4f580be24a7413269d25ce4dbc614e35 /sys/ufs
parentc23b0b441a985274551fcb108c06f12593545672 (diff)
downloadFreeBSD-src-ea417bf09acdf5d9f44a16d4325b3b99dda501e3.zip
FreeBSD-src-ea417bf09acdf5d9f44a16d4325b3b99dda501e3.tar.gz
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
Diffstat (limited to 'sys/ufs')
-rw-r--r--sys/ufs/ffs/ffs_vfsops.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/sys/ufs/ffs/ffs_vfsops.c b/sys/ufs/ffs/ffs_vfsops.c
index c099732..aa9f19a 100644
--- a/sys/ufs/ffs/ffs_vfsops.c
+++ b/sys/ufs/ffs/ffs_vfsops.c
@@ -1577,7 +1577,9 @@ ffs_vgetf(mp, ino, flags, vpp, ffs_flags)
*/
if (vp->v_type != VFIFO) {
/* FFS supports shared locking for all files except fifos. */
+ VI_LOCK(vp);
VN_LOCK_ASHARE(vp);
+ VI_UNLOCK(vp);
}
/*
OpenPOWER on IntegriCloud