All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <luis@igalia.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Joanne Koong <joannelkoong@gmail.com>,
	 Horst Birthelmer <horst@birthelmer.de>,
	 miklos@szeredi.hu,  fuse-devel@lists.linux.dev,
	linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v2 12/21] fuse: add struct fuse_entry2_out and helpers for extended entry replies
Date: Tue, 19 May 2026 16:26:28 +0100	[thread overview]
Message-ID: <87tss3ifob.fsf@igalia.com> (raw)
In-Reply-To: <CAOQ4uxj+ss82jZV6yq=LXag2s_ax9rVdtH9uc8W+RnRD+U5qpg@mail.gmail.com> (Amir Goldstein's message of "Tue, 19 May 2026 16:17:51 +0200")


(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 <joannelkoong@gmail.com> wrote:
>>
>> On Sat, May 16, 2026 at 12:29 PM Horst Birthelmer <horst@birthelmer.de> 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

  reply	other threads:[~2026-05-19 15:26 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16  0:39 [PATCH v2 00/21] fuse: extend passthrough to inode operations Joanne Koong
2026-05-16  0:39 ` [PATCH v2 01/21] fuse: introduce FUSE_PASSTHROUGH_INO mode Joanne Koong
2026-05-16  0:39 ` [PATCH v2 02/21] fuse: prepare for passthrough of inode operations Joanne Koong
2026-05-16  1:34   ` Joanne Koong
2026-05-16 16:11     ` Amir Goldstein
2026-05-18 18:04       ` Joanne Koong
2026-05-18 18:39         ` Amir Goldstein
2026-05-18 20:56           ` Joanne Koong
2026-05-16  0:39 ` [PATCH v2 03/21] fuse: prepare for readdir passthrough on directories Joanne Koong
2026-05-16  0:39 ` [PATCH v2 04/21] fuse: implement passthrough for readdir Joanne Koong
2026-05-16  0:39 ` [PATCH v2 05/21] fuse: prepare for long lived reference on backing file Joanne Koong
2026-05-16  0:39 ` [PATCH v2 06/21] fuse: implement passthrough for getattr/statx Joanne Koong
2026-05-16 12:42   ` Amir Goldstein
2026-05-16  0:39 ` [PATCH v2 07/21] fuse: prepare to setup backing inode passthrough on lookup Joanne Koong
2026-05-16  0:39 ` [PATCH v2 08/21] fuse: handle zero ops_mask in FUSE_DEV_IOC_BACKING_OPEN Joanne Koong
2026-05-16 15:35   ` Amir Goldstein
2026-05-16  0:39 ` [PATCH v2 09/21] fuse: handle partial io passthrough for read/write, splice, and mmap Joanne Koong
2026-05-16 16:57   ` Amir Goldstein
2026-05-16 18:34     ` Amir Goldstein
2026-05-18 21:46     ` Joanne Koong
2026-05-16  0:39 ` [PATCH v2 10/21] fuse: prepare to cache statx attributes from entry replies Joanne Koong
2026-05-16  0:39 ` [PATCH v2 11/21] fuse: clean up fuse_dentry_revalidate() Joanne Koong
2026-05-16  0:39 ` [PATCH v2 12/21] fuse: add struct fuse_entry2_out and helpers for extended entry replies Joanne Koong
2026-05-16 17:25   ` Amir Goldstein
2026-05-16 19:29     ` Horst Birthelmer
2026-05-18 23:12       ` Joanne Koong
2026-05-19 14:17         ` Amir Goldstein
2026-05-19 15:26           ` Luis Henriques [this message]
2026-05-19 22:07             ` Joanne Koong
2026-05-16  0:39 ` [PATCH v2 13/21] fuse: add passthrough lookup Joanne Koong
2026-05-16 21:11   ` Amir Goldstein
2026-05-16  0:39 ` [PATCH v2 14/21] fuse: add passthrough support for entry creation Joanne Koong
2026-05-16  0:39 ` [PATCH v2 15/21] fuse: add passthrough support for create+open Joanne Koong
2026-05-16  0:39 ` [PATCH v2 16/21] fuse: allow backing_id=0 in open to inherit inode's backing file Joanne Koong
2026-05-16 21:07   ` Amir Goldstein
2026-05-16  0:40 ` [PATCH v2 17/21] backing-inode: add backing_inode_copyattr() Joanne Koong
2026-05-16 21:32   ` Amir Goldstein
2026-05-18 23:21     ` Joanne Koong
2026-05-19 11:47       ` Amir Goldstein
2026-05-16  0:40 ` [PATCH v2 18/21] backing-inode: add backing_inode_setattr() Joanne Koong
2026-05-16 22:47   ` Amir Goldstein
2026-05-16  0:40 ` [PATCH v2 19/21] fuse: add passthrough setattr Joanne Koong
2026-05-16  1:04   ` Joanne Koong
2026-05-16 23:03     ` Amir Goldstein
2026-05-18 23:47       ` Joanne Koong
2026-05-16 22:29   ` Amir Goldstein
2026-05-16  0:40 ` [PATCH v2 20/21] fuse: use passthrough getattr in setattr suid/sgid handling Joanne Koong
2026-05-16  1:20   ` Joanne Koong
2026-05-16 22:23     ` Amir Goldstein
2026-05-19  0:01       ` Joanne Koong
2026-05-16  0:40 ` [PATCH v2 21/21] docs: fuse: document extended passthrough (FUSE_PASSTHROUGH_INO) Joanne Koong
2026-05-16 18:23   ` Amir Goldstein
2026-05-16 20:59     ` Amir Goldstein
2026-05-18 21:23       ` 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=87tss3ifob.fsf@igalia.com \
    --to=luis@igalia.com \
    --cc=amir73il@gmail.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=horst@birthelmer.de \
    --cc=joannelkoong@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.