linux-kernel - Re: [PATCH v4] fs: fuse: add more information to fdinfo

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] [day] [month] [year] [list]

Message-ID: <CAC1kPDMuAPV+3SwsqnNBLhQag73TLA5+HivQFcJ3m-QKHAGbXg@mail.gmail.com>
Date: Thu, 15 May 2025 14:41:23 +0800
From: Chen Linxuan <chenlinxuan@...ontech.com>
To: Chen Linxuan <chenlinxuan@...ontech.com>
Cc: Miklos Szeredi <miklos@...redi.hu>, 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 Thu, May 15, 2025 at 2:36 PM Chen Linxuan <chenlinxuan@...ontech.com> wrote:

> 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.

Oh I see I can get connection id via .st_dev from stat(2)