Page MenuHomeFreeBSD

fusefs: remove the obsolete rename_lock
ClosedPublic

Authored by asomers on Tue, Feb 10, 8:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Feb 28, 7:08 AM
Unknown Object (File)
Sat, Feb 21, 12:20 AM
Unknown Object (File)
Thu, Feb 19, 10:20 AM
Unknown Object (File)
Wed, Feb 18, 6:23 PM
Unknown Object (File)
Tue, Feb 17, 6:08 PM
Unknown Object (File)
Mon, Feb 16, 6:43 AM
Unknown Object (File)
Wed, Feb 11, 9:24 AM
Unknown Object (File)
Wed, Feb 11, 7:16 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