From: Neil Brown <neilb@suse.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Karel Zak <kzak@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
util-linux-ng@vger.kernel.org, linuxram@us.ibm.com,
viro@ftp.linux.org.uk, hch@infradead.org, a.p.zijlstra@chello.nl
Subject: Re: [patch] VFS: extend /proc/mounts
Date: Thu, 17 Jan 2008 11:33:09 +1100 [thread overview]
Message-ID: <18318.41541.386224.301640@notabene.brown> (raw)
In-Reply-To: message from Jan Engelhardt on Thursday January 17
On Thursday January 17, jengelh@computergmbh.de wrote:
>
> On Jan 17 2008 00:43, Karel Zak wrote:
> >>
> >> Seems like a plain bad idea to me. There will be any number of home-made
> >> /proc/mounts parsers and we don't know what they do.
> >
> > So, let's use /proc/mounts_v2 ;-)
>
> Was not it like "don't use /proc for new things"?
I thought it was "don't use /proc for new things that aren't process
related".
And as the mount table is per process......
A host has a bunch of mounted filesystems (struct super_block), and
each process has some subset of these stitched together into a mount
tree (struct vfsmount / struct namespace).
There needs to be something in /proc that exposes the vfsmount tree.
Arguably there should be something else - maybe in sysfs - that
provides access to the "struct superblock" object.
And there needs to be a clear way to relate information from one with
information from the other.
In the tradition of stat, statm, status, maybe the former should be
/proc/$PID/mountm
:-)
Hey, I just found /proc/X/mountstats. How does this fit in to the big
picture?
NeilBrown
next prev parent reply other threads:[~2008-01-17 0:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 22:12 [patch] VFS: extend /proc/mounts Miklos Szeredi
2008-01-16 22:30 ` Andrew Morton
2008-01-16 23:15 ` Miklos Szeredi
2008-01-16 23:43 ` Karel Zak
2008-01-16 23:58 ` Jan Engelhardt
2008-01-17 0:09 ` Andrew Morton
2008-01-17 3:35 ` Al Viro
2008-01-17 0:33 ` Neil Brown [this message]
2008-01-17 1:17 ` Jan Engelhardt
2008-01-17 8:55 ` Miklos Szeredi
2008-01-17 15:36 ` Chuck Lever
2008-01-17 2:45 ` H. Peter Anvin
2008-01-17 3:33 ` Al Viro
2008-01-17 8:36 ` Miklos Szeredi
2008-01-17 10:34 ` Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18318.41541.386224.301640@notabene.brown \
--to=neilb@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=util-linux-ng@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox