From: Andrew Morton <akpm@linux-foundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@zeniv.linux.org.uk, linuxram@us.ibm.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/7] vfs: mountinfo (v3)
Date: Wed, 26 Mar 2008 15:06:55 -0700 [thread overview]
Message-ID: <20080326150655.43e9acd7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080326211131.705321084@szeredi.hu>
On Wed, 26 Mar 2008 22:11:31 +0100 Miklos Szeredi <miklos@szeredi.hu> wrote:
> Here's an updated mountinfo patch with the following changes relative
> to the last submission (the one currently in -mm):
>
> - in __d_path() don't add extra parameter for checking unreachable path
> - reduce proliferation of #ifdef CONFIG_PROC_FS into dcache.c and seq_file.c
> - make peer group ID allocation a separate pass from setting mount shared
> - change order and format of fields in /proc/<pid>/mountinfo
> - remove dubious cleanups
> - consolidate locking: don't use vfsmount_lock where namespace_sem suffices
> - patch history was getting tangled up, merge and resplit into logical chunks
>
> This series is also available here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git mountinfo
I coudn't get that to work, perhaps due to lack of gittiness.
> I guess the simplest for all involved parties would be if this went
> into Al's tree (if it looks OK) and then Andrew can suck that tree (*)
> containing all sort of goodies into -mm.
>
> (*) git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git vfs-2.6.25
I recently added that tree to the -mm lineup as git-vfs.patch, and it's in
linux-next.
This patch series applied happily on top of git-vfs (and 887 other patches ;))
prev parent reply other threads:[~2008-03-26 22:07 UTC|newest]
Thread overview: 15+ 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
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 ` Andrew Morton [this message]
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=20080326150655.43e9acd7.akpm@linux-foundation.org \
--to=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 \
--cc=viro@zeniv.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 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.