Page MenuHomeFreeBSD

fusefs: fix two bugs regarding VOP_RECLAIM of the root inode
ClosedPublic

Authored by asomers on Apr 2 2022, 7:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Feb 25, 11:39 PM
Unknown Object (File)
Mon, Feb 24, 4:12 PM
Unknown Object (File)
Sun, Feb 16, 3:33 AM
Unknown Object (File)
Feb 7 2025, 10:08 PM
Unknown Object (File)
Jan 21 2025, 7:19 AM
Unknown Object (File)
Jan 17 2025, 1:54 PM
Unknown Object (File)
Dec 23 2024, 6:14 AM
Unknown Object (File)
Dec 10 2024, 1:33 AM
Subscribers

Details

Summary
  • We never send FUSE_LOOKUP for the root inode, since its inode number is hard-coded to 1. Therefore, we should not send FUSE_FORGET for it, lest the server see its lookup count fall below 0.
  • During VOP_RECLAIM, if we are reclaiming the root inode, we must clear the file system's vroot pointer. Otherwise it will be left pointing at a reclaimed vnode, which will cause future VOP_LOOKUP operations to fail. Previously we only cleared that pointer during VFS_UMOUNT. I don't know of any real-world way to trigger this bug.

MFC after: 2 weeks

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 44972
Build 41860: arc lint + arc unit

Event Timeline

Release root inode even if the server is already detached

This revision is now accepted and ready to land.Apr 4 2022, 3:29 AM