linux-kernel - Re: [patch] VFS: extend /proc/mounts

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: <88976638-FBF2-45CB-9ED3-500ED2623916@oracle.com>
Date:	Thu, 17 Jan 2008 10:36:24 -0500
From:	Chuck Lever <chuck.lever@...cle.com>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	neilb@...e.de, jengelh@...putergmbh.de, kzak@...hat.com,
	akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, util-linux-ng@...r.kernel.org,
	linuxram@...ibm.com, viro@....linux.org.uk, hch@...radead.org,
	a.p.zijlstra@...llo.nl
Subject: Re: [patch] VFS: extend /proc/mounts

On Jan 17, 2008, at 3:55 AM, Miklos Szeredi wrote:
>> Hey, I just found /proc/X/mountstats.  How does this fit in to the  
>> big
>> picture?
>
> It seems to show some counters for NFS mounts, no other filesystem
> uses it.  Format looks rather less nice, than /proc/X/mounts (why do
> we need long english sentences under /proc?).

I introduced /proc/self/mountstats because we need a way for non- 
block-device-based file systems to report I/O statistics.  Everything  
else I tried was rejected, and apparently what we ended up with was  
reviewed by only a handful of people, so no one else likes it or uses  
it.

It can go away for all I care, as long as we retain some flexible  
mechanism for non-block-based file systems to report I/O stats.  As  
far as I am aware, there are only two user utilities that understand  
and parse this data, and I maintain both.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/