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>] [day] [month] [year] [list]
Date: Fri, 22 Mar 2024 15:25:16 +0000
From: Josh Triplett <josh@...htriplett.org>
To: Alessio Balsini <balsini@...roid.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: FUSE passthrough after opening?

I'm really happy to see the FUSE passthrough support merged!

I have a use case for which it'd be nice to start FUSE passthrough
some time after the initial open: I have a network-backed filesystem,
and in some cases I'd like to serve an initial request before retrieving
the full file. For instance, for a library .so file, I'd love to service
the initial 832-byte read while still downloading the full file.

Would it be possible to add support for transitioning an open FUSE file
to being backed by passthrough *after* the initial open? Could that work
with the current passthrough architecture? (I realize that this might be
more complex, as the initial open is a good time to directly substitute
a file from the underlying filesystem.)

Thanks,
Josh Triplett

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ