Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754580AbYJFORX (ORCPT ); Mon, 6 Oct 2008 10:17:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752539AbYJFORP (ORCPT ); Mon, 6 Oct 2008 10:17:15 -0400 Received: from e36.co.us.ibm.com ([32.97.110.154]:37066 "EHLO e36.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752513AbYJFORO (ORCPT ); Mon, 6 Oct 2008 10:17:14 -0400 Date: Mon, 6 Oct 2008 09:11:01 -0500 From: "Serge E. Hallyn" To: James Morris Cc: David Howells , Andrew Morton , Linux Containers , lkml Subject: Re: [PATCH 1/3] user namespaces: introduce user_struct->user_namespace relationship Message-ID: <20081006141101.GB15419@us.ibm.com> References: <20081004013644.GA24104@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1476 Lines: 34 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. 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/