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: <CANXojcwP2jQUpXSZAv_3z5q+=Zrn7M8ffh2_KdcZpEad+XH6_A@mail.gmail.com>
Date: Thu, 6 Nov 2025 17:08:00 +0100
From: Stef Bon <stefbon@...il.com>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Amir Goldstein <amir73il@...il.com>, Bernd Schubert <bschubert@....com>, 
	Luis Henriques <luis@...lia.com>, Bernd Schubert <bernd@...ernd.com>, "Theodore Ts'o" <tytso@....edu>, 
	Miklos Szeredi <miklos@...redi.hu>, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Kevin Chen <kchen@....com>
Subject: Re: [RFC] Another take at restarting FUSE servers

Hi,

is implementing a lookup using a handle to be in the kernel?

I've written a FUSE fs for sftp using SSH as transport, where the
lookup call normally has to create a path (relative to the root of the
sftp) and send that to the remote server.
It saves the creation of this path if there is a handle available.
When doing an opendir, this is normally followed by a lookup for every
dentry. (sftp does not support readdirplus) Now in this case there is
a handle available (the one used by opendir, or one created with
open), so the fuse daemon I wrote used that to proceed. (and so not
create a path).

So it can also go in userspace.

Stef

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ