linux-kernel - Re: [PATCH] fuse: show the io

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: <CAJnrk1b28v4RWvVN5LWwMiqTtqC=wWPQhSQJ-dkYQyaFvjbVPQ@mail.gmail.com>
Date: Mon, 29 Dec 2025 13:31:24 -0800
From: Joanne Koong <joannelkoong@...il.com>
To: Bernd Schubert <bernd@...ernd.com>
Cc: Kuang Kai <kuangkai@...inos.cn>, miklos@...redi.hu, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org, kk47yx@...il.com
Subject: Re: [PATCH] fuse: show the io_uring mount option

On Thu, Dec 25, 2025 at 1:34 PM Bernd Schubert <bernd@...ernd.com> wrote:
>
>
>
> On 12/25/25 06:50, Kuang Kai wrote:
> > From: kuangkai <kuangkai@...inos.cn>
> >
> > mount with io_uring options will not work if the kernel parameter of /sys/module/fuse/parameters/enable_uring has not been set,
> > displaying this option can help confirm whether the fuse over io_uring function is enabled.
>
> The problem is that is io_uring is not a mount option, showing it as
> such would not be right. Maybe showing all FUSE_INIT parameters should
> be added in /sys?

Or maybe showing all FUSE_INIT parameters through libfuse to something
like /var/run/$UID/libfuse instead of doing it through /sys/fs/ and
the kernel? I think other connection state could be added there too,
eg the name or pid corresponding to the server.

Thanks,
Joanne

>
> Thanks,
> Bernd
>