- Don't drop the lock in ufs_inactive().
- Also in ufs_inactive, don't acquire the vnode interlock where it isn't strictly needed. Also owning the vnode interlock while calling vprint() will cause locking assertions to trip. Sponsored by: Isilon Systems, Inc.
This commit is contained in:
parent
0463dc9ef1
commit
38d504db44
@ -74,11 +74,8 @@ ufs_inactive(ap)
|
||||
mode_t mode;
|
||||
int error = 0;
|
||||
|
||||
VI_LOCK(vp);
|
||||
if (prtactive && vp->v_usecount != 0)
|
||||
vprint("ufs_inactive: pushing active", vp);
|
||||
VI_UNLOCK(vp);
|
||||
|
||||
/*
|
||||
* Ignore inodes related to stale file handles.
|
||||
*/
|
||||
@ -122,7 +119,6 @@ ufs_inactive(ap)
|
||||
}
|
||||
}
|
||||
out:
|
||||
VOP_UNLOCK(vp, 0, td);
|
||||
/*
|
||||
* If we are done with the inode, reclaim it
|
||||
* so that it can be reused immediately.
|
||||
|
Loading…
Reference in New Issue
Block a user