Page MenuHomeFreeBSD

vfs_unregister: fix error handling
ClosedPublic

Authored by vangyzen on Feb 25 2022, 3:41 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Mar 20, 1:14 AM
Unknown Object (File)
Jan 14 2024, 5:17 AM
Unknown Object (File)
Jan 10 2024, 3:41 AM
Unknown Object (File)
Nov 22 2023, 9:37 AM
Unknown Object (File)
Nov 21 2023, 5:41 PM
Unknown Object (File)
Nov 13 2023, 2:57 PM
Unknown Object (File)
Nov 13 2023, 10:26 AM
Unknown Object (File)
Nov 11 2023, 2:32 PM
Subscribers

Details

Summary

Due to misplaced braces, an error from vfs_uninit() in the VFCF_SBDRY
case was ignored.

Reported by: Anton Rang <rang@acm.org>
MFC after: 1 week
Sponsored by: Dell EMC Isilon

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Feb 25 2022, 3:44 PM

Because of this bug, the nfs VFS module was incorrectly unloaded. However, the nfscl module still refused to unload, so the result was mostly harmless, meaning the kernel didn't panic. The worst effect was, NFS was no longer listed as a VFS, so no NFS mounts could be created until the next reboot. Amusingly, kldload failed with EOPNOTSUPP before and after the fix, so I had to use dtrace to see the difference.

This revision was automatically updated to reflect the committed changes.