All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	lkml <linux-kernel@vger.kernel.org>,
	jmorris@us.ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)
Date: Fri, 24 Oct 2008 14:18:13 -0500	[thread overview]
Message-ID: <20081024191813.GA27505@us.ibm.com> (raw)
In-Reply-To: <11290.1224873841@redhat.com>

Quoting David Howells (dhowells@redhat.com):
> Serge E. Hallyn <serue@us.ibm.com> wrote:
> 
> > I've just tested with David's plain creds-v3 tree
> 
> Note the creds-v4 branch is now current.  Is it worth me replacing that with a
> tree that just has a master branch to simplify things?

I saw it in your list of branches, but linux-next/Next/Trees still
listed v3 so i figured i should test against that.

> > -	struct user_namespace *ns = current->nsproxy->user_ns;
> > +	struct user_namespace *ns = current_user()->user_ns;
> 
> current_user_ns() perchance?

Yes, thanks.  (Of course that doesn't break anything so if the patch is
otherwise ok i've written down a note to send a follow-up patch)

thanks,
-serge

  reply	other threads:[~2008-10-24 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 17:48 [PATCH] User namespaces: set of cleanups (v2) Serge E. Hallyn
2008-10-24 18:44 ` David Howells
2008-10-24 19:18   ` Serge E. Hallyn [this message]
2008-10-24 19:40     ` David Howells
2008-10-25  2:08   ` Stephen Rothwell
2008-10-26 11:07     ` David Howells
2008-10-26 11:53       ` Stephen Rothwell
2008-10-26 16:04         ` David Howells
2008-10-26 16:11         ` David Howells
2008-10-25  2:05 ` Stephen Rothwell
2008-10-28 16:21   ` Serge E. Hallyn
2008-10-29  7:36     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-10-20 23:01 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=20081024191813.GA27505@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=dhowells@redhat.com \
    --cc=jmorris@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.