From: "Serge E. Hallyn" <serue@us.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: James Morris <jmorris@namei.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkml <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Michael Halcrow <mhalcrow@us.ibm.com>
Subject: Re: [PATCH] User namespaces: set of cleanups (eventually for linux-next?)
Date: Mon, 20 Oct 2008 13:51:30 -0500 [thread overview]
Message-ID: <20081020185130.GA21054@us.ibm.com> (raw)
In-Reply-To: <758.1224201299@redhat.com>
Quoting David Howells (dhowells@redhat.com):
>
> Serge E. Hallyn <serue@us.ibm.com> wrote:
>
> > David, since this consumes your patch, I wasn't sure whether it was
> > appropriate to put your signed-off-by on here or not. I decided
> > doing so was the worse of the potential offenses...
>
> The way I think I'd've done it is to include my patch description and
> signed-off-by then list your additional changes (just keep on incrementing the
> point numbers) and your signed-off-by.
>
> > - new_user = alloc_uid(current->nsproxy->user_ns, new->uid);
> > + new_user = alloc_uid(current_user()->user_ns, new->uid);
>
> That should be current_user_ns() rather than current_user()->user_ns. I made
> this change before adding the macro.
Ok, will change.
> > + key_put(new->thread_keyring);
> > + new->thread_keyring = NULL;
>
> Superfluous. copy_creds() does this immediately upon return.
Oops, will drop.
> Also, in copy_creds(), should the session and process keyrings be discarded if
> CLONE_NEWUSER is set? Actually, I think that should be dealt with by a patch
> to deal with namespacing keyrings as the user-default keyrings need to be
> namespaced rather than here.
>
> David
Oh, yeah, that's going to have to be a separate patch I guess...
thanks,
-serge
prev parent reply other threads:[~2008-10-20 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 22:46 [PATCH] User namespaces: set of cleanups (eventually for linux-next?) Serge E. Hallyn
2008-10-16 23:17 ` James Morris
2008-10-16 23:54 ` David Howells
2008-10-20 18:51 ` Serge E. Hallyn [this message]
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=20081020185130.GA21054@us.ibm.com \
--to=serue@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox