Page MenuHomeFreeBSD

fusefs: add more tests for buggy FUSE servers
ClosedPublic

Authored by asomers on Jan 15 2025, 8:22 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 5, 12:16 PM
Unknown Object (File)
Thu, Nov 27, 9:33 AM
Unknown Object (File)
Wed, Nov 26, 9:53 PM
Unknown Object (File)
Mon, Nov 24, 3:36 PM
Unknown Object (File)
Mon, Nov 24, 9:03 AM
Unknown Object (File)
Sat, Nov 22, 9:03 AM
Unknown Object (File)
Thu, Nov 20, 1:43 AM
Unknown Object (File)
Fri, Nov 14, 5:02 AM
Subscribers

Details

Summary
  • If a FUSE file system is NFS-exported (either by a kernel or userspace NFS server), then it must support FUSE_LOOKUP operations for ".". But if the response reports a different nodeid than the request, that's very bad. Fail the operation and warn the operator.
  • In general, a FUSE file may have a distinct "nodeid" and "inode number". But it the file system is NFS-exported (either by a kernel or userspace NFS server), then those two must match, because the NFS server will do VFS_VGET operations using the inode number. If they don't match, warn the operator.

MFC after: 2 weeks
Sponsored by: ConnectWise

Test Plan

Test cases added

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable