All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com
Subject: Re: [PATCH 1/3] user namespaces: introduce user_struct->user_namespace relationship
Date: Wed, 27 Aug 2008 17:07:40 -0700	[thread overview]
Message-ID: <20080827170740.c50cacf7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080826185341.GA338@us.ibm.com>

On Tue, 26 Aug 2008 13:53:41 -0500
"Serge E. Hallyn" <serue@us.ibm.com> wrote:

> When a task does clone(CLONE_NEWNS), the task's user is the 'creator' of the
> new user_namespace, and the user_namespace is tacked onto a list of those
> created by this user.
> 
> Changelog:
> 	Aug 25: make free_user not inlined as it's not trivial.  (Eric
> 		Biederman suggestion)
> 	Aug 1: renamed user->user_namespace to user_ns, as the next
> 		patch did anyway.
> 	Aug 1: move put_user_ns call in one free_user() definition
> 		to move it outside the lock in free_user.  put_user_ns
> 		calls free_user on the user_ns->creator, which in
> 		turn would grab the lock again.
> 
> Signed-off-by: Serge Hallyn <serue@us.ibm.com>
> ---
>  include/linux/sched.h          |    1 +
>  include/linux/user_namespace.h |    1 +
>  kernel/user.c                  |   11 +++++++++--
>  kernel/user_namespace.c        |   20 +++++++++++---------

The credentials code in linux-next is changing the same code which
you're changing, in more-than-trivially-textual ways.

I'd suggest a dhowells cc on these changes, as he's also working
in this area, and as you touch the keyring code a bit.

And, of course, please remove that almost-always-wrong
extern-declaration-in-C which checkpatch told you about.  init_groups
is already declared in include/linux/init_task.h anyway...


  parent reply	other threads:[~2008-08-28  0:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 18:53 [PATCH 1/3] user namespaces: introduce user_struct->user_namespace relationship Serge E. Hallyn
2008-08-26 18:55 ` [PATCH 2/3] user namespaces: move user_ns from nsproxy into user struct Serge E. Hallyn
2008-08-26 18:56 ` [PATCH 3/3] user namespaces: reset task's credentials on CLONE_NEWUSER Serge E. Hallyn
2008-08-28  0:07 ` Andrew Morton [this message]
2008-08-28  0:52   ` [PATCH 1/3] user namespaces: introduce user_struct->user_namespace relationship Serge E. Hallyn
  -- strict thread matches above, loose matches on Subject: below --
2008-10-04  1:36 Serge E. Hallyn
2008-10-05 21:50 ` 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
     [not found]         ` <20081007170539.GA525-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-10-07 21:08           ` James Morris
2008-10-07 21:08             ` James Morris
2008-08-02  0:54 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=20080827170740.c50cacf7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /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.