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)
Thu, Sep 17, 9:15 PM
Unknown Object (File)
Thu, Sep 17, 5:58 AM
Unknown Object (File)
Mon, Sep 14, 12:59 PM
Unknown Object (File)
Fri, Sep 11, 7:08 PM
Unknown Object (File)
Wed, Sep 9, 7:03 PM
Unknown Object (File)
Sun, Sep 6, 7:39 PM
Unknown Object (File)
Fri, Sep 4, 5:33 PM
Unknown Object (File)
Wed, Sep 2, 4:43 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