linux-kernel - Re: [RFC PATCH v1 3/3] fuse: implementation of the FUSE_LOOKUP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6e561ea7-f7dd-4c94-854e-83c2fb9b0133@ddn.com>
Date: Fri, 21 Nov 2025 09:06:42 +0000
From: Bernd Schubert <bschubert@....com>
To: Amir Goldstein <amir73il@...il.com>, Luis Henriques <luis@...lia.com>
CC: Miklos Szeredi <miklos@...redi.hu>, "Darrick J. Wong" <djwong@...nel.org>,
	Kevin Chen <kchen@....com>, Horst Birthelmer <hbirthelmer@....com>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Matt Harvey
	<mharvey@...ptrading.com>, "kernel-dev@...lia.com" <kernel-dev@...lia.com>
Subject: Re: [RFC PATCH v1 3/3] fuse: implementation of the FUSE_LOOKUP_HANDLE
 operation

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@...lia.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