Page MenuHomeFreeBSD

fusefs: remove the obsolete rename_lock
ClosedPublic

Authored by asomers on Feb 10 2026, 8:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, May 15, 2:27 AM
Unknown Object (File)
Fri, May 15, 2:19 AM
Unknown Object (File)
Fri, May 15, 12:25 AM
Unknown Object (File)
Wed, May 13, 6:11 PM
Unknown Object (File)
Tue, May 12, 4:17 PM
Unknown Object (File)
Tue, May 12, 4:57 AM
Unknown Object (File)
Thu, May 7, 1:24 PM
Unknown Object (File)
Tue, May 5, 12:39 AM
Subscribers

Details

Summary

This lock was included in the original GSoC submission. Its purpose
seems to have been to prevent concurrent FUSE_RENAME operations for the
current mountpoint, as well as to synchronse FUSE_RENAME with
fuse_vnode_setparent. But it's obsolete, now that ef6ea91593e added
mnt_renamelock .

MFC after: 2 weeks
Sponsored by: ConnectWise

Test Plan

Used existing test suite

Diff Detail

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