Date: Tue, 7 Oct 2008 12:05:39 -0500
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: David Howells <dhowells@redhat.com>, Andrew Morton <akpm@osdl.org>,
       Linux Containers <containers@lists.osdl.org>,
       lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] user namespaces: introduce
	user_struct->user_namespace relationship
Message-ID: <20081007170539.GA525@us.ibm.com>
References: <20081004013644.GA24104@us.ibm.com> <alpine.LRH.1.10.0810060846020.30516@tundra.namei.org> <20081006141101.GB15419@us.ibm.com> <alpine.LRH.1.10.0810070847480.4113@tundra.namei.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.1.10.0810070847480.4113@tundra.namei.org>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2431
Lines: 55

Quoting James Morris (jmorris@namei.org):
> On Mon, 6 Oct 2008, Serge E. Hallyn wrote:
> 
> > Quoting James Morris (jmorris@namei.org):
> > > On Fri, 3 Oct 2008, Serge E. Hallyn wrote:
> > > 
> > > > Hi James,
> > > > 
> > > > here are 3 patches to fix up the user namespaces a bit in preparation
> > > > for real userns work to begin.  Andrew had suggested that these be
> > > > rebased on top of your -next tree because they will conflict with
> > > > the credentials work.  But it looks like much of the credentials stuff
> > > > isn't in your next branch.  If you'd prefer that I port these to
> > > > creds-next, please let me know.  I'll have to do it eventually :)
> > > 
> > > creds-next is dead.
> > > 
> > > Code ready for the next merge window is in the 'next' branch, while the 
> > > current creds code is in the 'creds-next-subsys' branch, which hasn't been 
> > > picked up in linux-next yet because of LPC and sfr's vacation.
> > > 
> > > When do you expect these patches to be sent upstream?  Are they ready now 
> > > as an incremental change for 2.6.27?
> > 
> > Oh I'm not trying to get them into 2.6.28, I'm just trying to get them
> > more widely tested, hopefully aiming for 2.6.29.  They have been stable
> > in all of my tests, and the last patch fixes a real (behavioral - not
> > oops-inducing) bug in the current code, but I'm trying to figure out
> > which path they should take.
> 
> I suggest feeding them into linux-next directly until you want them merged 
> with another tree.  Are there known clashes with the creds work?  If so, 

Certainly with the overall creds work.  I haven't looked in
creds-next-subsys yet to see if it conflicts.  I'll go ahead and port
later this week or early next.

> the fixups could be carried in linux-next, or generate them against 
> creds-next-subsys for inclusion after that.

creds-next-subsys is not yet feeding into linux-next, right?  So I
should wait until they hit linux-next?

(It makes more sense for me to port userns on top of creds than for
David to port creds on top of my patches anyway.  I'm actually a bit
afraid that my refcounting will be complicated by struct creds, but
we'll see)

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