From: Andrew Morton <akpm@linux-foundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: 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: Wed, 16 Jan 2008 14:30:51 -0800 [thread overview]
Message-ID: <20080116143051.ec488f3d.akpm@linux-foundation.org> (raw)
In-Reply-To: <E1JFGUp-00054z-KQ@pomaz-ex.szeredi.hu>
On Wed, 16 Jan 2008 23:12:31 +0100
Miklos Szeredi <miklos@szeredi.hu> wrote:
> The reason, why this patch was dug up, is that if the bdi-sysfs patch
> is going to use device numbers to identify BDIs, then there should be
> a way for the user to map the device number into mount(s).
>
> But it's useful regardless of the bdi-sysfs patch.
Don't know what that is.
> Can this be added to -mm?
>
> In theory it could break userspace, but I think it's very unlikely to
> do so, because stuff is added only at the end of the lines, and
> because most programs probably parse it through the libc interface
> which is not broken by this change. Despite this, it should be tested
> on as many systems as possible.
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.
> - for mount ID's use IRA instead of a 32bit counter, which could overflow
don't know what an IRA is.
> - print canonical ID's (smallest one within the peer group) for peers
> and master, this is more useful, than a random ID within the same namespace
> - fix a couple of small bugs
> - style fixes
>
> Signed-off-by: Ram Pai <linuxram@us.ibm.com>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Both the newly-added inlines in this patch are wrong. They will result in
a larger and slower kernel. This should be very well known by now.
next prev parent reply other threads:[~2008-01-16 22:35 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 [this message]
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
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=20080116143051.ec488f3d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hch@infradead.org \
--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