linux-kernel - Re: [RFC PATCH] fs: fuse: add backing

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: <CAC1kPDPY=qpGNRO3CH6_jSMKh6RyfHPFw71gCcpBZ-ogG41psA@mail.gmail.com>
Date: Thu, 8 May 2025 01:03:08 +0800
From: Chen Linxuan <chenlinxuan@...ontech.com>
To: Amir Goldstein <amir73il@...il.com>
Cc: Chen Linxuan <chenlinxuan@...ontech.com>, Miklos Szeredi <miklos@...redi.hu>, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] fs: fuse: add backing_files control file

On Thu, May 8, 2025 at 12:57 AM Amir Goldstein <amir73il@...il.com> wrote:

> It means everything to userspace.
> backing ids are part of the userspace UAPI - you have documented it yourself.
> The fuse server used backing ids to manage access to backing files
> https://github.com/libfuse/libfuse/blob/master/example/passthrough_hp.cc#L855

Oh, I see.

> This is extra and nice to have.
> It can show admin which files are using fuse passthrough.
> It cannot replace displaying all backing ids under connection
> because server can register backing ids without using them to open files
> and most importantly server can leak backing ids, which is a good
> reason to kill it.

I will have a try later.