linux-kernel - Re: [RFC PATCH v2 4/6] 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: <b2582658-c5e9-4cf8-b673-5ccc78fe0d75@ddn.com>
Date: Fri, 9 Jan 2026 16:56:26 +0100
From: Bernd Schubert <bschubert@....com>
To: Miklos Szeredi <miklos@...redi.hu>, Amir Goldstein <amir73il@...il.com>
Cc: Luis Henriques <luis@...lia.com>, "Darrick J. Wong" <djwong@...nel.org>,
 Kevin Chen <kchen@....com>, Horst Birthelmer <hbirthelmer@....com>,
 linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
 Matt Harvey <mharvey@...ptrading.com>, kernel-dev@...lia.com
Subject: Re: [RFC PATCH v2 4/6] fuse: implementation of the FUSE_LOOKUP_HANDLE
 operation

On 1/9/26 16:37, Miklos Szeredi wrote:
> On Fri, 9 Jan 2026 at 16:03, Amir Goldstein <amir73il@...il.com> wrote:
> 
>> What about FUSE_CREATE? FUSE_TMPFILE?
> 
> FUSE_CREATE could be decomposed to FUSE_MKOBJ_H + FUSE_STATX + FUSE_OPEN.
> 
> FUSE_TMPFILE is special, the create and open needs to be atomic.   So
> the best we can do is FUSE_TMPFILE_H + FUSE_STATX.
> 
>> and more importantly READDIRPLUS dirents?
> 
> I was never satisfied with FUSE_READDIRPLUS, I'd prefer something more
> flexible, where policy is moved from the kernel to the fuse server.
> 
> How about a push style interface with FUSE_NOTIFY_ENTRY setting up the
> dentry and the inode?

Feasible, but we should extend io-uring to FUSE_NOTIFY first, otherwise
this will have a painful overhead.

Thanks,
Bernd