7f7aad09bd
VOP_RECLAIM naturally has exclusive access to the vnode, so having it locked on entry is not strictly necessary -- but it means if there are any final operations that must be done on the vnode, such as ffs_update, requiring exclusive access to it, we can now kassert that the vnode is locked in those operations. We can't just have the caller release the last lock because some file systems don't use genfs_lock, and require the vnode to remain valid for VOP_UNLOCK to work, notably unionfs. |
||
|---|---|---|
| .. | ||
| Makefile | ||
| files.procfs | ||
| procfs.h | ||
| procfs_auxv.c | ||
| procfs_cmdline.c | ||
| procfs_ctl.c | ||
| procfs_fd.c | ||
| procfs_fpregs.c | ||
| procfs_linux.c | ||
| procfs_map.c | ||
| procfs_mem.c | ||
| procfs_note.c | ||
| procfs_regs.c | ||
| procfs_status.c | ||
| procfs_subr.c | ||
| procfs_vfsops.c | ||
| procfs_vnops.c | ||