Page MenuHomeFreeBSD

fusefs: ensure that FUSE ops' headers' unique values are actually unique
ClosedPublic

Authored by asomers on Jun 18 2021, 12:18 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 14, 8:03 PM
Unknown Object (File)
Sep 24 2024, 1:17 AM
Unknown Object (File)
Sep 12 2024, 6:36 AM
Unknown Object (File)
Sep 8 2024, 3:24 PM
Unknown Object (File)
Sep 3 2024, 4:51 AM
Unknown Object (File)
Aug 17 2024, 7:59 PM
Unknown Object (File)
Aug 13 2024, 6:04 PM
Unknown Object (File)
Aug 11 2024, 10:15 PM
Subscribers

Details

Summary

fusefs: delete dead code

It was always dead, accidentally included in SVN r345876.

MFC after: 2 weeks

fusefs: also debug INIT operations in the test suite

MFC after: 2 weeks

fusefs: ensure that FUSE ops' headers' unique values are actually unique

Every FUSE operation has a unique value in its header. As the name
implies, these values are supposed to be unique among all outstanding
operations. And since FUSE_INTERRUPT is asynchronous and racy, it is
desirable that the unique values be unique among all operations that are
"close in time".

Ensure that they are actually unique by incrementing them whenever we
reuse a fuse_dispatcher object, for example during fsync, write, and
listextattr.

PR: 244686
MFC after: 2 weeks

Test Plan

Assertions added to existing test suite.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 39968
Build 36857: arc lint + arc unit