Re: [post LSFMM summary] where is fuse going?

[Luis Henriques <luis@igalia.com>]

Hi Miklos,

On Mon, May 11 2026, Miklos Szeredi wrote:

> Please let know what I missed.

Thanks for the summary.  It looks pretty comprehensive to me, the only
things I don't see listed are the FUSE discord and the monthly/biweekly
call.  But that's probably out of the scope of this email.

Also...

[snip]

> COMPOUND REQS: let's add this to fusex.  uAPI is simple, kAPI needs refining.
>
> FILE HANDLES: same: let's add to fusex.

I'd like to clarify this: do you see fusex as some sort of staging area
for features development that would (or could) eventually be merged back
into the "traditional" FUSE?

I'm asking because I got under the impression that file handles in
particular was something that would be desired to have in "traditional"
FUSE (and that's where I would rather have them TBH).  This would, for
example, help unbreak nfs exports.

Cheers,
-- 
Luís


> URING BUFFER MANAGEMENT: there's a disagreement between Joanne and
> Bernd about this.  I think we first need a very high level description
> of each solution and why it's preferred over the other.
>
> LARGE FOLIOS: depends on !strictlimit.  I don't have a good enough
> understanding of writeback throttling to decide whether removing the
> strictlimit requirement for unprivileged fuse is okay or not.  Need
> more analysis.
>
> FUSEX: there was approval for the idea of using this as a uAPI major
> version update.  In other words fusex will gain feature parity with
> legacy fuse, but with a more consistent interface.
>
> MAILING LIST: we have a shiny new one, there was agreement that it's
> sufficient for normal fuse discussion and patch posting, and usually
> there's no need to cross post linux-fsdevel.
>
> Amir asked about how long it took for overlayfs to go upstream.  Well,
> I looked up both fuse and overlayfs:
>
> fuse first release: Nov 2001
> fuse merge: Sep 2005
>
> ovl first patchset: Aug 2010
> ovl merge: Oct 2014
>
> Both 4 years ±2 months.
>
> So don't despair! There's light at the end of the tunnel (and
> hopefully not the oncoming train ;)
>
> Thanks,
> Miklos