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)
Sun, Jul 5, 4:01 PM
Unknown Object (File)
Sun, Jul 5, 4:01 PM
Unknown Object (File)
Sun, Jun 28, 10:15 AM
Unknown Object (File)
Sat, Jun 27, 9:29 PM
Unknown Object (File)
Wed, Jun 24, 8:04 AM
Unknown Object (File)
Fri, Jun 19, 1:05 AM
Unknown Object (File)
Sat, Jun 13, 8:19 PM
Unknown Object (File)
Wed, Jun 10, 12:06 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