From: Horst Birthelmer <horst@birthelmer.de>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: fuse-devel@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fuse: add fusex filesystem
Date: Mon, 11 May 2026 10:50:00 +0200 [thread overview]
Message-ID: <agGW6FCbnIyy_OuE@fedora.fritz.box> (raw)
In-Reply-To: <20260429102058.1362965-1-mszeredi@redhat.com>
On Wed, Apr 29, 2026 at 12:20:57PM +0200, Miklos Szeredi wrote:
> This stands for "fuse extended/experimental".
>
> 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.
>
> Whether these features will be migrated back into the main fuse codebase,
> or fusex is going to end up as a major version update is still up in the
> air.
>
> Major differences from regular fuse:
>
> - local filesystem mode only
> - only synchronous FUSE_INIT is supported
> - only no-open mode
> - new requests:
> + FUSE_LOOKUP_ROOT - return nodeid of root
> + FUSE_LOOKUPX - FUSE_LOOKUP without the getattr
> + FUSE_MKOBJX - merged FUSE_MKNOD, MKDIR, SYMLINK and TMPFILE
> + FUSE_SETSTATX - extended version of FUSE_SETATTR
>
> Missing features:
>
> - file handles / export ops
> - compound requests
> - xattr caching
> - fileattr
> - fiemap
> - ioctl
> - copy_file_range
> - lazy dir open
>
> Test server can be found at:
>
> https://github.com/szmi/fuse-utils
>
> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
> ---
>
Hi Miklos,
I have patched passthrough_hp to use fusex and have noticed, that I had to do
the following to make it work:
diff --git a/fs/fuse/fusex.c b/fs/fuse/fusex.c
index 98e239e7e00e..87fcfc16645a 100644
--- a/fs/fuse/fusex.c
+++ b/fs/fuse/fusex.c
@@ -14,6 +14,7 @@
#include <linux/statfs.h>
#include <linux/falloc.h>
#include <linux/fs_parser.h>
+#include <uapi/linux/magic.h>
static void fusex_init_inode(struct inode *inode);
@@ -1337,6 +1338,7 @@ static int fusex_send_opendir(struct fuse_file *ff, struct inode *inode)
if (!err) {
ff->fh = outarg.fh;
ff->open_flags = FOPEN_CACHE_DIR;
+ ff->nodeid = get_node_id(inode);
}
return err;
}
---
After that I could actually mount and do simple meta operations.
The nodeid is used for listing.
Thanks,
Horst
next prev parent reply other threads:[~2026-05-11 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 10:20 [PATCH] fuse: add fusex filesystem Miklos Szeredi
2026-05-07 8:31 ` Horst Birthelmer
2026-05-08 13:01 ` Amir Goldstein
2026-05-12 8:17 ` Miklos Szeredi
2026-05-12 13:08 ` Amir Goldstein
2026-05-12 13:46 ` Bernd Schubert
2026-05-12 8:11 ` Miklos Szeredi
2026-05-12 10:29 ` Horst Birthelmer
2026-05-08 17:29 ` Horst Birthelmer
2026-05-12 8:20 ` Miklos Szeredi
2026-05-11 8:50 ` Horst Birthelmer [this message]
2026-05-12 8:34 ` Miklos Szeredi
2026-05-12 5:05 ` Joanne Koong
2026-05-12 9:18 ` Miklos Szeredi
2026-05-12 13:22 ` Amir Goldstein
2026-05-12 19:22 ` Joanne Koong
2026-05-12 17:33 ` Joanne Koong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=agGW6FCbnIyy_OuE@fedora.fritz.box \
--to=horst@birthelmer.de \
--cc=fuse-devel@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox