linux-kernel - Re: [patch 0/7] vfs: mountinfo (v3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080326150655.43e9acd7.akpm@linux-foundation.org>
Date:	Wed, 26 Mar 2008 15:06:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	viro@...iv.linux.org.uk, linuxram@...ibm.com,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 0/7] vfs: mountinfo (v3)

On Wed, 26 Mar 2008 22:11:31 +0100 Miklos Szeredi <miklos@...redi.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 ;))

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/