vnode: remove VLOCKSWORK and check locking when vop_islocked != nullop
authorsemarie <semarie@openbsd.org>
Tue, 19 Oct 2021 06:26:08 +0000 (06:26 +0000)
committersemarie <semarie@openbsd.org>
Tue, 19 Oct 2021 06:26:08 +0000 (06:26 +0000)
commit10dc078528519b6d34f2083e65dda8cc55239771
tree9a4aa0f8ed642831d299f85e8dc396695f914c08
parent4f12c8ab063383cd7d25f15b13b7a1240c0c5dc3
vnode: remove VLOCKSWORK and check locking when vop_islocked != nullop

This flag is currently used to mark or unmark a vnode to actively
check vnode locking semantic (when compiled with VFSLCKDEBUG).

Currently, VLOCKSWORK flag isn't properly set for several FS
implementation which have full locking support. This commit enable
proper checking for them too (cd9660, udf, fuse, msdosfs, tmpfs).

Instead of using a particular flag, it directly check if
v_op->vop_islocked is nullop or not to activate or not the vnode
locking checks.

ok mpi@
sys/kern/vfs_subr.c
sys/kern/vfs_vops.c
sys/nfs/nfs_node.c
sys/sys/vnode.h
sys/ufs/ext2fs/ext2fs_subr.c
sys/ufs/ffs/ffs_subr.c
sys/ufs/ffs/ffs_vfsops.c
sys/uvm/uvm_vnode.c