freebsd-skq/sys/fs/nwfs
mckusick 25230d4c6a Regularize the vop_stdlock'ing protocol across all the filesystems
that use it. Specifically, vop_stdlock uses the lock pointed to by
vp->v_vnlock. By default, getnewvnode sets up vp->v_vnlock to
reference vp->v_lock. Filesystems that wish to use the default
do not need to allocate a lock at the front of their node structure
(as some still did) or do a lockinit. They can simply start using
vn_lock/VOP_UNLOCK. Filesystems that wish to manage their own locks,
but still use the vop_stdlock functions (such as nullfs) can simply
replace vp->v_vnlock with a pointer to the lock that they wish to
have used for the vnode. Such filesystems are responsible for
setting the vp->v_vnlock back to the default in their vop_reclaim
routine (e.g., vp->v_vnlock = &vp->v_lock).

In theory, this set of changes cleans up the existing filesystem
lock interface and should have no function change to the existing
locking scheme.

Sponsored by:	DARPA & NAI Labs.
2002-10-14 03:20:36 +00:00
..
nwfs_io.c - Replace v_flag with v_iflag and v_vflag 2002-08-04 10:29:36 +00:00
nwfs_ioctl.c Return ENOTTY on unrecognized ioctls. 2002-09-26 14:08:37 +00:00
nwfs_mount.h More s/file system/filesystem/g 2002-05-16 21:28:32 +00:00
nwfs_node.c Regularize the vop_stdlock'ing protocol across all the filesystems 2002-10-14 03:20:36 +00:00
nwfs_node.h KSE Milestone 2 2001-09-12 08:38:13 +00:00
nwfs_subr.c Add a missing #include <sys/lockmgr.h>. 2002-09-01 23:02:10 +00:00
nwfs_subr.h KSE Milestone 2 2001-09-12 08:38:13 +00:00
nwfs_vfsops.c - Use vrefcnt() where it is safe to do so instead of doing direct and 2002-09-25 02:32:42 +00:00
nwfs_vnops.c - Use vrefcnt() where it is safe to do so instead of doing direct and 2002-09-25 02:32:42 +00:00
nwfs.h KSE Milestone 2 2001-09-12 08:38:13 +00:00