Lines Matching full:vnode

68 functions will increment the reference count for the vnode in question.
69 The reference count has to be decremented after use of the vnode, by
172 Lock vnode on return with
189 function return the parent (directory) vnode,
206 function to return the parent (directory) vnode in an unlocked state.
207 The parent vnode must be released separately by using
222 of the path supplied is a symbolic link (i.e., it will return a vnode
235 necessary a directory, and lookup returns the vnode for this file.
237 Lock vnode on return with
239 if permitted by the file system that owns the vnode.
246 when allocating the vnode.
249 is specified but shared locking is not permitted, then the vnode will be
324 This allows to weaken the lock mode of the return vnode, if the
331 lookup leading to mount root, returns the root vnode of
332 the mount instead of the covered vnode of the filesystem where
342 Audit the looked up vnode information, use the first slot for audit information.
382 Usually implies a need to specially handle the vnode locking
383 for instantiation of the target vnode.
412 Vnode pointer to directory of the object on which lookup is performed.
422 Vnode pointer to the resulting object,
427 field of this vnode is incremented.
452 Only relative lookups were done to resolve the path to vnode.
493 	... use nd.ni_vp vnode
530 .Xr vnode 9 ,
543 flag does not always result in the parent vnode being locked.