Page MenuHomeFreeBSD

fusefs: remove the obsolete rename_lock
ClosedPublic

Authored by asomers on Feb 10 2026, 8:48 PM.
Tags
None
Referenced Files
F164537978: D55231.diff
Sat, Aug 1, 11:08 PM
F164537972: D55231.diff
Sat, Aug 1, 11:07 PM
F164499427: D55231.diff
Sat, Aug 1, 11:18 AM
Unknown Object (File)
Fri, Jul 31, 2:02 PM
Unknown Object (File)
Fri, Jul 31, 2:02 PM
Unknown Object (File)
Tue, Jul 21, 7:04 PM
Unknown Object (File)
Tue, Jul 21, 1:58 AM
Unknown Object (File)
Sat, Jul 18, 8:33 PM
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