Page MenuHomeFreeBSD

vfs: fully hold vnodes in vnlru_free_locked
ClosedPublic

Authored by mjg on Sep 4 2019, 6:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sep 27 2024, 2:32 PM
Unknown Object (File)
Sep 22 2024, 6:02 PM
Unknown Object (File)
Sep 18 2024, 12:05 PM
Unknown Object (File)
Sep 18 2024, 6:56 AM
Unknown Object (File)
Sep 8 2024, 1:26 PM
Unknown Object (File)
Sep 8 2024, 11:55 AM
Unknown Object (File)
Sep 8 2024, 3:11 AM
Unknown Object (File)
Aug 31 2024, 11:37 AM
Subscribers

Details

Summary

Currently the code only bumps holdcnt and clears the VI_FREE flag, not performing actual vhold. Since the vnode is still visible elsewhere, a potential new user can find it and incorrectly assume it is properly held. Use vholdl to properly hold the vnode.

The other place recycling (vlrureclaim) does this already. This probably can be hacked to avoid most of the work, but that's for later.

Test Plan

reduced maxvnodes to 20000 and tested with suj11.sh from stress2. constant recycles with no issues.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Sep 4 2019, 6:43 PM
This revision was automatically updated to reflect the committed changes.