From: Al Viro <viro@ZenIV.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linuxram@us.ibm.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 6/7] vfs: mountinfo: add /proc/<pid>/mountinfo
Date: Wed, 26 Mar 2008 22:44:55 +0000 [thread overview]
Message-ID: <20080326224455.GV10722@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20080326212143.479034123@szeredi.hu>
On Wed, Mar 26, 2008 at 10:11:37PM +0100, Miklos Szeredi wrote:
> +This file contains lines of the form:
> +
> +36 35 98:0 /mnt1 /mnt2 rw,noatime rw master:1 - ext3 /dev/root,errors=continue
> +(1)(2)(3) (4) (5) (6) (7) (8) (9) (10) (11) (12)
> +
> +(1) mount ID: unique identifier of the mount (may be reused after umount)
> +(2) parent ID: ID of parent (or of self for the top of the mount tree)
> +(3) major:minor: value of st_dev for files on filesystem
> +(4) root: root of the mount within the filesystem
> +(5) mount point: mount point relative to the process's root
> +(6) mount options: per mount options
> +(7) super options: filesystem type independent, per super block options
Move that one past fs type, please.
> +(8) optional fields: zero or more fields of the form "tag[:value]"
> +(9) separator: marks the end of the optional fields
> +(10) filesystem type: name of filesystem of the form "type[.subtype]"
> +(11) mount source: filesystem specific information or "none"
I'm not even sure that we *want* "none" here, to be honest, but that's
a separate story...
next prev parent reply other threads:[~2008-03-26 22:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 21:11 [patch 0/7] vfs: mountinfo (v3) Miklos Szeredi
2008-03-26 21:11 ` [patch 1/7] vfs: mountinfo: add dentry_path() Miklos Szeredi
2008-03-26 21:11 ` [patch 2/7] vfs: mountinfo: add seq_file_root() Miklos Szeredi
2008-03-26 21:11 ` [patch 3/7] vfs: mountinfo: add mount ID Miklos Szeredi
2008-03-26 22:25 ` Al Viro
2008-03-26 21:11 ` [patch 4/7] vfs: mountinfo: add mount peer group ID Miklos Szeredi
2008-03-26 22:39 ` Al Viro
2008-03-26 21:11 ` [patch 5/7] vfs: mountinfo: allow using process root Miklos Szeredi
2008-03-26 21:11 ` [patch 6/7] vfs: mountinfo: add /proc/<pid>/mountinfo Miklos Szeredi
2008-03-26 22:44 ` Al Viro [this message]
2008-03-27 8:33 ` Miklos Szeredi
2008-03-26 21:11 ` [patch 7/7] vfs: mountinfo: show dominating group id Miklos Szeredi
2008-03-26 22:51 ` Al Viro
2008-03-27 8:34 ` Miklos Szeredi
2008-03-26 22:06 ` [patch 0/7] vfs: mountinfo (v3) Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-03-27 12:06 [patch 0/7] vfs: mountinfo (v4) Miklos Szeredi
2008-03-27 12:06 ` [patch 6/7] vfs: mountinfo: add /proc/<pid>/mountinfo Miklos Szeredi
2008-03-27 22:36 ` Al Viro
2008-03-28 8:48 ` Miklos Szeredi
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=20080326224455.GV10722@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.