FUSEX File-System Being Developed For Extended/Experimental Features
Miklos Szeredi of Red Hat is developing FUSEX, a new file-system designed as an experimental extension of FUSE for Linux. FUSEX aims to provide a cleaner codebase for major feature development, such as the FUSE_IOMAP API, without risking stability in the main FUSE code. The project is currently in development on kernel.org and includes a test implementation on GitHub.
- ▪Miklos Szeredi of Red Hat is leading the development of the FUSEX file-system.
- ▪FUSEX is intended to support big feature work like the FUSE_IOMAP API in a safer, isolated environment.
- ▪The FUSEX code is being developed in the 'fusex' branch on FUSE.git at kernel.org, with a test implementation available on GitHub.
- ▪FUSEX currently supports only synchronous FUSE_INIT and lacks several features present in regular FUSE, such as xattr caching and ioctl.
- ▪It remains uncertain whether FUSEX features will be merged back into FUSE or become a major version update.
- ▪FUSEX introduces new requests like FUSE_LOOKUP_ROOT, FUSE_LOOKUPX, FUSE_MKOBJX, and FUSE_SETSTATX.
Opening excerpt (first ~120 words) tap to expand
FUSEX File-System Being Developed For Extended/Experimental Features Written by Michael Larabel in Linux Storage on 2 May 2026 at 06:00 PM EDT. 3 Comments Miklos Szeredi of Red Hat has been developing the FUSEX file-system as an extended/experimental area for File-System in User-Space "FUSE" development. One of the leading motivators to the development of FUSEX is working to provide a clean codebase for big feature work being spurred on by pursuing the FUSE_IOMAP API. Szeredi added in the patch message: "The purpose is to provide a clean base for big features like the FUSE_IOMAP api. It's also a good way to try new stuff like file handles and compound requests without the risk of breaking something in the large and complex fuse codebase.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Phoronix.