Kirk McKusick a5b65058d5 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
..
pseudofs_fileno.c	Gratuitous whitespace cleanup.	2002-06-06 16:59:24 +00:00
pseudofs_internal.h	[the previous commit to pseudofs_vncache.c got the wrong log message]	2001-10-01 04:26:33 +00:00
pseudofs_vncache.c	Regularize the vop_stdlock'ing protocol across all the filesystems	2002-10-14 03:20:36 +00:00
pseudofs_vnops.c	- Use vrefcnt() where it is safe to do so instead of doing direct and	2002-09-25 02:32:42 +00:00
pseudofs.c	Remove all use of vnode->v_tag, replacing with appropriate substitutes.	2002-09-14 09:02:28 +00:00
pseudofs.h	Introduce support for Mandatory Access Control and extensible	2002-08-01 01:33:12 +00:00