Re: [PATCH v2 12/21] fuse: add struct fuse_entry2_out and helpers for extended entry replies

(Sorry, I'm slow catching-up with email :-) )

On Tue, May 19 2026, Amir Goldstein wrote:

> On Tue, May 19, 2026 at 1:12 AM Joanne Koong <[email protected]> wrote:
>>
>> On Sat, May 16, 2026 at 12:29 PM Horst Birthelmer <[email protected]> wrote:
> ...
>> > Hi Amir,
>> >
>> > I see there is a lot of talk about using the compounds in a couple of different contexts.
>> > I really have to apologize for not having the latest patch ready by now, but I'm
>> > a bit unsure how to do it.
>> >
>> > I'm not entirely sure if compounds will only be a thing for fusex or if it will ever
>> > be accepted for the classic FUSE.
>>
>> I'm not sure what the plan is either. I think this will get clarified
>> on Thursday hopefully.

From Miklos' email "[post LSFMM summary] where is fuse going?"[1] I
thought the plan was clear: both compound and file handles are going to be
in fusex.  Quoting:

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


[1] https://lore.kernel.org/all/CAJfpegvXnA1QpmfM9V+3VB470xYDNWH8FV0mBV1R1-HqvjfJ8A@mail.gmail.com

> Wait, is there a FUSE call? I did not get an invite :-D

Don't worry, I think no one has yet received an invite ;-)

Cheers,
-- 
Luís