2008-03-26 21:23:51

by Miklos Szeredi

[permalink] [raw]
Subject: [patch 0/7] vfs: mountinfo (v3)

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 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

Thanks,
Miklos

--


2008-03-26 22:07:32

by Andrew Morton

[permalink] [raw]
Subject: Re: [patch 0/7] vfs: mountinfo (v3)

On Wed, 26 Mar 2008 22:11:31 +0100 Miklos Szeredi <[email protected]> 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 ;))