freebsd-dev/sys/security/lomac
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
..
kernel_interface.c
kernel_interface.h
kernel_lkm.c
kernel_log.c
kernel_log.h
kernel_mediate.c
kernel_mediate.h
kernel_mmap.c
kernel_monitor.c
kernel_monitor.h
kernel_pipe.c
kernel_pipe.h
kernel_plm.c
kernel_plm.h
kernel_socket.c
kernel_socket.h
kernel_util.c
kernel_util.h
lomac.h
lomacfs_subr.c
lomacfs_vfsops.c
lomacfs_vnops.c Regularize the vop_stdlock'ing protocol across all the filesystems 2002-10-14 03:20:36 +00:00
lomacfs.h
lomacio.h
policy_plm.h
syscall_gate.c
syscall_gate.h