From: Christoph Hellwig <hch@infradead.org>
To: Ram Pai <linuxram@us.ibm.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Al Viro <viro@ftp.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, util-linux-ng@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] VFS: Augment /proc/mount with subroot and shared-subtree
Date: Sat, 30 Jun 2007 10:44:46 +0100 [thread overview]
Message-ID: <20070630094446.GB22889@infradead.org> (raw)
In-Reply-To: <1182808816.2816.7.camel@ram.us.ibm.com>
On Mon, Jun 25, 2007 at 03:00:15PM -0700, Ram Pai wrote:
> Please check if the following modified patch meets the requirements.
>
> It augments /proc/mount with additional information to
> (1) disambiguate bind mounts with subroot information.
> (2) display shared-subtree information using which one can
> determine the propagation trees.
>
>
> The following additional fields are appended to each record
> in /proc/mounts
NACK. Adding anything to the format will confuse the hell out of
existing parsers. We really want something like your /proc/<pid>/mounts_new,
except mounts_new should have a better name (/proc/<pid>/ns anyone? :))
next prev parent reply other threads:[~2007-06-30 9:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 20:57 Adding subroot information to /proc/mounts, or obtaining that through other means H. Peter Anvin
2007-06-20 21:03 ` Al Viro
2007-06-20 21:20 ` H. Peter Anvin
2007-06-21 16:20 ` Ram Pai
2007-06-21 16:29 ` H. Peter Anvin
2007-06-21 17:20 ` Ram Pai
2007-06-21 17:31 ` H. Peter Anvin
2007-06-21 17:43 ` H. Peter Anvin
2007-06-22 6:44 ` Ram Pai
2007-06-22 7:06 ` H. Peter Anvin
2007-06-22 7:34 ` Ram Pai
2007-06-22 7:51 ` H. Peter Anvin
[not found] ` <20070625214640.GC29058@ram.us.ibm.com>
2007-06-25 22:00 ` [RFC PATCH 1/1] VFS: Augment /proc/mount with subroot and shared-subtree Ram Pai
2007-06-26 8:01 ` Karel Zak
2007-06-26 14:34 ` H. Peter Anvin
2007-06-30 9:44 ` Christoph Hellwig [this message]
2007-06-30 12:56 ` H. Peter Anvin
2007-07-11 10:24 ` Christoph Hellwig
2007-07-11 15:42 ` Ram Pai
2007-07-16 18:46 ` [RFC2 " Ram Pai
2007-06-20 22:24 ` Adding subroot information to /proc/mounts, or obtaining that through other means Karel Zak
2007-06-20 22:39 ` H. Peter Anvin
2007-06-20 22:33 ` Chuck Lever
2007-06-20 22:41 ` H. Peter Anvin
2007-06-20 22:48 ` Chuck Lever
2007-06-20 22:57 ` H. Peter Anvin
2007-06-20 23:02 ` Chuck Lever
2007-06-21 16:13 ` H. Peter Anvin
2007-06-21 16:49 ` Serge E. Hallyn
2007-06-21 16:51 ` H. Peter Anvin
2007-06-28 14:53 ` Pavel Machek
2007-06-28 15:36 ` H. Peter Anvin
2007-06-20 22:05 ` Karel Zak
2007-06-20 22:07 ` H. Peter Anvin
2007-06-20 22:41 ` Dr. David Alan Gilbert
2007-06-20 22:46 ` H. Peter Anvin
2007-06-21 19:14 ` Hans-Peter Jansen
2007-06-21 19:19 ` H. Peter Anvin
2007-06-20 22:55 ` Nix
2007-06-21 10:45 ` Miklos Szeredi
2007-06-21 19:42 ` Nix
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=20070630094446.GB22889@infradead.org \
--to=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--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
all inboxes | Powered by JetHome®