linux-kernel - Re: [PATCH 2/7] proc: Implement support for automounts in task directories

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: <20081119023507.GA5888@x200.localdomain>
Date:	Wed, 19 Nov 2008 05:35:07 +0300
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, viro@...IV.linux.org.uk,
	containers@...ts.osdl.org
Subject: Re: [PATCH 2/7] proc: Implement support for automounts in task
	directories

On Wed, Nov 19, 2008 at 03:07:49AM +0300, Alexey Dobriyan wrote:
> On Thu, Nov 13, 2008 at 03:39:44PM -0800, Eric W. Biederman wrote:
> > On this patchset it looks like the conversation has wound down with no
> > real objects except that some very simple pieces of the code appear
> > magic.
> > 
> > 
> > What looks to be the best path for getting this set of patches merged
> > into /proc?
> 
> Al's ACK minimum.
> 
> > Alexy will you pick this up in your /proc tree as Andrew suggested?
> 
> Yep, doing it right now.
> 
> > Do I need to keep my own tree?
> 
> No need.
> 
> > Can I have some clear guidance on which hurdles to jump through to
> > make forward progress?

OK, I fixed some small issues and pushed out to proc.git so it starts
propagate to -next.
--
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/