From: Luis Henriques <luis@igalia.com>
To: Bernd Schubert <bschubert@ddn.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
"Darrick J. Wong" <djwong@kernel.org>,
Kevin Chen <kchen@ddn.com>,
Horst Birthelmer <hbirthelmer@ddn.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matt Harvey <mharvey@jumptrading.com>,
"kernel-dev@igalia.com" <kernel-dev@igalia.com>
Subject: Re: [RFC PATCH v1 3/3] fuse: implementation of the FUSE_LOOKUP_HANDLE operation
Date: Fri, 21 Nov 2025 10:00:59 +0000 [thread overview]
Message-ID: <878qfzn1r8.fsf@wotan.olymp> (raw)
In-Reply-To: <6e561ea7-f7dd-4c94-854e-83c2fb9b0133@ddn.com> (Bernd Schubert's message of "Fri, 21 Nov 2025 09:06:42 +0000")
On Fri, Nov 21 2025, Bernd Schubert wrote:
> Thanks a lot for this Luis!
>
> On 11/21/25 08:49, Amir Goldstein wrote:
>> On Thu, Nov 20, 2025 at 11:55 AM Luis Henriques <luis@igalia.com> wrote:
>>>
>>> The implementation of LOOKUP_HANDLE simply modifies the LOOKUP operation to
>>> include an extra inarg: the file handle for the parent directory (if it is
>>> available). Also, because fuse_entry_out now has a extra variable size
>>> struct (the actual handle), it also sets the out_argvar flag to true.
>>>
>>> Most of the other modifications in this patch are a fallout from these
>>> changes: because fuse_entry_out has been modified to include a variable size
>>> struct, every operation that receives such a parameter have to take this
>>> into account:
>>>
>>> CREATE, LINK, LOOKUP, MKDIR, MKNOD, READDIRPLUS, SYMLINK, TMPFILE
>>>
>>
>> Overall, this is exactly what I had in mind.
>> Maybe it's utter garbage but that's what I was aiming for ;)
>>
>> I'd like to get feedback from Miklos and Bernd on the details of the
>> protocol extension, especially w.r.t backward compat aspects.
>
> I will look into it in the late afternoon
That'd be awesome, thanks a lot Bernd!
Cheers,
--
Luís
next prev parent reply other threads:[~2025-11-21 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:55 [RFC PATCH v1 0/3] fuse: LOOKUP_HANDLE operation Luis Henriques
2025-11-20 10:55 ` [RFC PATCH v1 1/3] fuse: initial infrastructure for FUSE_LOOKUP_HANDLE support Luis Henriques
2025-11-20 10:55 ` [RFC PATCH v1 2/3] fuse: move fuse_entry_out structs out of the stack Luis Henriques
2025-11-20 10:55 ` [RFC PATCH v1 3/3] fuse: implementation of the FUSE_LOOKUP_HANDLE operation Luis Henriques
2025-11-21 7:49 ` Amir Goldstein
2025-11-21 9:06 ` Bernd Schubert
2025-11-21 10:00 ` Luis Henriques [this message]
2025-11-21 9:59 ` Luis Henriques
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=878qfzn1r8.fsf@wotan.olymp \
--to=luis@igalia.com \
--cc=amir73il@gmail.com \
--cc=bschubert@ddn.com \
--cc=djwong@kernel.org \
--cc=hbirthelmer@ddn.com \
--cc=kchen@ddn.com \
--cc=kernel-dev@igalia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mharvey@jumptrading.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox