[Bug 238197] [FUSEFS] fusefs supports neither chflags(2) not stat.st_birthtim
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue May 28 20:21:42 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238197
Bug ID: 238197
Summary: [FUSEFS] fusefs supports neither chflags(2) not
stat.st_birthtim
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: asomers at FreeBSD.org
Created attachment 204675
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=204675&action=edit
Add st_birthtime support to FUSEFS backwards-incompatibly
The FUSE protocol does not support chflags(2) at all, and the FUSE_GETATTR and
FUSE_SETATTR messages have no fields for st_birthtime. This is a direct result
of its Linux-only origins. OSXFuse extended the protocol to add those features
(and others), but they had to fork libfuse to do it. FreeBSD has thus far had
a policy of no changes to libfuse. Even if we were to abandon that policy, we
can't add chflags and st_birthtime support without bumping the FUSE kernel API
version past the most recently published version in libfuse. The reason is
because libfuse includes its own copy of the kernel API header. Changing the
FUSE protocol without reving the kernel API past what is already published by
libfuse would thus break existing binaries.
Attached is a patch that adds st_birthtime support to fusefs(5). However, it
adds it at protocol version 7.9, so it breaks compatibility with existing
binaries. The patch also includes some OSX definitions. I thought that
including them would make it easier to update libfuse.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list