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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 2 Apr 2020 16:14:24 +0200
From:   Karel Zak <>
To:     Ian Kent <>
Cc:     Miklos Szeredi <>,
        David Howells <>,
        Linus Torvalds <>,
        Al Viro <>,
        Linux NFS list <>,
        Andreas Dilger <>,
        Anna Schumaker <>,
        Theodore Ts'o <>,
        Linux API <>,,
        Trond Myklebust <>,
        Miklos Szeredi <>,
        Christian Brauner <>,
        Jann Horn <>,
        "Darrick J. Wong" <>,
        Jeff Layton <>,,
        LSM <>,
Subject: Re: [PATCH 00/13] VFS: Filesystem information [ver #19]

On Thu, Apr 02, 2020 at 09:38:20AM +0800, Ian Kent wrote:
> I prefer the system call interface and I'm not offering justification
> for that other than a general dislike (and on occasion outright
> frustration) of pretty much every proc implementation I have had to
> look at.

Frankly, I'm modest, what about to have both interfaces in kernel --
fsinfo() as well mountfs? It's nothing unusual for example for block
devices to have attribute accessible by /sys as well as by ioctl().

I can imagine that for complex task or performance sensitive tasks
it's better to use fsinfo(), but in another simple use-cases (for
example to convert mountpoint to device name in shell) is better to
read /proc/.../<atrtr>.


 Karel Zak  <>

Powered by blists - more mailing lists