Re: Re: Re: [PATCH v5 1/3] fuse: add compound command to combine multiple requests

From: Miklos Szeredi

Date: Mon Feb 16 2026 - 06:43:48 EST


On Sat, 14 Feb 2026 at 18:51, Horst Birthelmer <horst@xxxxxxxxxxxxx> wrote:

> Which part would process those interdependencies?
> We have multiple options and I'm not entirely sure,
> the kernel, libfuse, fuse server?

Kernel: mandatory
Libfuse: new versions should handle it, but older versions continue to
work (because the kernel will deal with it)
Fuse server: optional

> In the current version none would do any special interpretation and the
> fuse server will have a specialized handler for a compound type, which
> automatically 'knows' how to get the right args.

The API should allow the server to deal with generic compounds, not
just combinations it actually knows about.

What we need to define is the types of dependencies, e.g.:

- default: wait for previous and stop on error
- copy nodeid in fuse_entry_out from the previous lookup/mk*
- copy fh in fuse_open_out from previous open

Thanks,
Miklos