public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 7 Oct 2008 12:05:39 -0500	[thread overview]
Message-ID: <20081007170539.GA525@us.ibm.com> (raw)
In-Reply-To: <alpine.LRH.1.10.0810070847480.4113@tundra.namei.org>

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

  reply	other threads:[~2008-10-07 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04  1:36 [PATCH 1/3] user namespaces: introduce user_struct->user_namespace relationship Serge E. Hallyn
2008-10-04  1:37 ` [PATCH 2/3] user namespaces: move user_ns from nsproxy into user struct Serge E. Hallyn
2008-10-04  1:37 ` [PATCH 3/3] user namespaces: reset task's credentials on CLONE_NEWUSER Serge E. Hallyn
2008-10-05 21:50 ` [PATCH 1/3] user namespaces: introduce user_struct->user_namespace relationship James Morris
2008-10-06 14:11   ` Serge E. Hallyn
2008-10-06 21:50     ` James Morris
2008-10-07 17:05       ` Serge E. Hallyn [this message]
2008-10-07 21:08         ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2008-08-26 18:53 Serge E. Hallyn
2008-08-28  0:07 ` Andrew Morton
2008-08-28  0:52   ` Serge E. Hallyn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081007170539.GA525@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=containers@lists.osdl.org \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox