Page MenuHomeFreeBSD

fusefs: remove the obsolete rename_lock
ClosedPublic

Authored by asomers on Feb 10 2026, 8:48 PM.
Tags
None
Referenced Files
F175168205: D55231.id172450.diff
Thu, Oct 8, 7:58 PM
Unknown Object (File)
Tue, Oct 6, 12:21 AM
Unknown Object (File)
Mon, Oct 5, 4:00 PM
Unknown Object (File)
Sat, Oct 3, 2:44 PM
Unknown Object (File)
Fri, Oct 2, 6:43 PM
Unknown Object (File)
Fri, Oct 2, 1:16 PM
Unknown Object (File)
Fri, Oct 2, 12:20 PM
Unknown Object (File)
Thu, Oct 1, 2:59 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