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: <CAC1kPDNvU-F=09Dsm1DW43Xrm1e4T3BQ0K5j7R1PHrQ-Ju0i6g@mail.gmail.com>
Date: Thu, 15 May 2025 14:36:09 +0800
From: Chen Linxuan <chenlinxuan@...ontech.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Chen Linxuan <chenlinxuan@...ontech.com>, Amir Goldstein <amir73il@...il.com>, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] fs: fuse: add more information to fdinfo

On Mon, May 12, 2025 at 2:55 PM Miklos Szeredi <miklos@...redi.hu> wrote:

> What I meant is adding this to fuse_dev_operations.

But it doesn't seem like exposing this information here would be a bad
idea either, does it?
For example, if a system administrator wants to write a script to
abort the FUSE connection
corresponding to a specific directory,
the script could use this information to locate the relevant connection.

Thanks,
Chen Linxuan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ