vop_revoke(9) [suse man page]

VOP_REVOKE(9)						   BSD Kernel Developer's Manual					     VOP_REVOKE(9)

NAME

     VOP_REVOKE -- revoke access to a device and its aliases

SYNOPSIS

     #include <sys/param.h>
     #include <sys/vnode.h>

     int
     VOP_REVOKE(struct vnode *vp, int flags);

DESCRIPTION

     VOP_REVOKE() will administratively revoke access to the device specified by vp, as well as any aliases created via make_dev_alias(9).  Fur-
     ther file operations on any of these devices by processes which have them open will nominally fail.  The flags must be set to REVOKEALL to
     signify that all access will be revoked; any other value is invalid.

LOCKS

     The vp must be unlocked on entry, and will remain unlocked upon return.

SEE ALSO

     make_dev_alias(9), vnode(9)

AUTHORS

     This manual page was written by Brian Fundakowski Feldman.

BSD
								 February 5, 2002							       BSD

VRELE(9)						   BSD Kernel Developer's Manual						  VRELE(9)

NAME

     vput, vrele, vunref -- decrement the use count for a vnode

SYNOPSIS

     #include <sys/param.h>
     #include <sys/vnode.h>

     void
     vput(struct vnode *vp);

     void
     vrele(struct vnode *vp);

     void
     vunref(struct vnode *vp);

DESCRIPTION

     Decrement the v_usecount field of a vnode.

     vp  the vnode to decrement

     The vrele() function takes an unlocked vnode and returns with the vnode unlocked.

     The vput() function should be given a locked vnode as argument, the vnode is unlocked after the function returned.  The vput() is opera-
     tionally equivalent to calling VOP_UNLOCK(9) followed by vrele(9), with less overhead.

     The vunref() function takes a locked vnode as argument, and returns with the vnode locked.

     Any code in the system which signified its use of a vnode by usecount should call one of the listed function to decrement use counter.  If
     the v_usecount field of the non-doomed vnode reaches zero, then it will be inactivated and placed on the free list.  Since the functions
     might need to call VOPs for the vnode, the Giant mutex should be conditionally locked around the call.

     The hold count for the vnode is always greater or equal to the usecount.  Non-forced unmount fails when mount point owns a vnode that has
     non-zero usecount, see vflush(9).

SEE ALSO

     vget(9), vnode(9), vref(9), vrefcnt(9)

AUTHORS

     This manual page was written by Doug Rabson and
     Konstantin Belousov.

BSD
								 November 20, 2010							       BSD