Date: Sun, 26 Oct 2025 17:44:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 290547] [fusefs]: kernel unconditionally sends FUSE_SETXATTR requests in extended format Message-ID: <bug-290547-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290547 Bug ID: 290547 Summary: [fusefs]: kernel unconditionally sends FUSE_SETXATTR requests in extended format Product: Base System Version: 15.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: asomers@FreeBSD.org In FUSE protocols 7.1 through 7.32, the FUSE_SETXATTR request includes an 8-byte header. Protocol 7.33 optionally extends that to 16 bytes, but only if the server sets FUSE_SETXATTR_EXT in its reply to FUSE_INIT. Ever since d5e3cf41e89400e75da87aad0cc9bde108e2573b FreeBSD 15.0-CURRENT has used the extended format. However, it has wrongly used that extended format even if the server does not set FUSE_SETXATTR_EXT. FreeBSD 14.3 and earlier are unaffected. This bug only affects file systems that use protocol 7.33 or later, and do _not_ set FUSE_SETXATTR_EXT. So anything using libfuse is unaffected, as are any Rust-based file systems using the popular fuse3 or fuser crates. I don't know of any off-the-shelf file systems that are affected. This issue was originally reported on Github by user CismonX. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-290547-227>