public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: adobriyan@gmail.com, kosaki.motohiro@jp.fujitsu.com,
	mingo@elte.hu, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix recursive lock in free_uid()/free_user_ns()
Date: Mon, 23 Feb 2009 14:33:56 -0600	[thread overview]
Message-ID: <20090223203356.GA30533@us.ibm.com> (raw)
In-Reply-To: <20090223125554.30814.79080.stgit@warthog.procyon.org.uk>

Quoting David Howells (dhowells@redhat.com):
> free_uid() and free_user_ns() are corecursive when CONFIG_USER_SCHED=n, but
> free_user_ns() is called from free_uid() by way of uid_hash_remove(), which
> requires uidhash_lock to be held.  free_user_ns() then calls free_uid() to
> complete the destruction.
> 
> Fix this by deferring the destruction of the user_namespace.

Crap.  I think when I did this I looked at put_user_ns() I though it
was calling free_user_ns() through an rcu callback (mis-read kref_put).

> Signed-off-by: David Howells <dhowells@redhat.com>

Acked-by: Serge Hallyn <serue@us.ibm.com>

Thanks, David and Alexey.

-serge

> ---
> 
>  include/linux/user_namespace.h |    1 +
>  kernel/user_namespace.c        |   21 +++++++++++++++++----
>  2 files changed, 18 insertions(+), 4 deletions(-)
> 
> 
> diff --git a/include/linux/user_namespace.h b/include/linux/user_namespace.h
> index 315bcd3..cc4f453 100644
> --- a/include/linux/user_namespace.h
> +++ b/include/linux/user_namespace.h
> @@ -13,6 +13,7 @@ struct user_namespace {
>  	struct kref		kref;
>  	struct hlist_head	uidhash_table[UIDHASH_SZ];
>  	struct user_struct	*creator;
> +	struct work_struct	destroyer;
>  };
> 
>  extern struct user_namespace init_user_ns;
> diff --git a/kernel/user_namespace.c b/kernel/user_namespace.c
> index 7908431..076c7c8 100644
> --- a/kernel/user_namespace.c
> +++ b/kernel/user_namespace.c
> @@ -60,12 +60,25 @@ int create_user_ns(struct cred *new)
>  	return 0;
>  }
> 
> -void free_user_ns(struct kref *kref)
> +/*
> + * Deferred destructor for a user namespace.  This is required because
> + * free_user_ns() may be called with uidhash_lock held, but we need to call
> + * back to free_uid() which will want to take the lock again.
> + */
> +static void free_user_ns_work(struct work_struct *work)
>  {
> -	struct user_namespace *ns;
> -
> -	ns = container_of(kref, struct user_namespace, kref);
> +	struct user_namespace *ns =
> +		container_of(work, struct user_namespace, destroyer);
>  	free_uid(ns->creator);
>  	kfree(ns);
>  }
> +
> +void free_user_ns(struct kref *kref)
> +{
> +	struct user_namespace *ns =
> +		container_of(kref, struct user_namespace, kref);
> +
> +	INIT_WORK(&ns->destroyer, free_user_ns_work);
> +	schedule_work(&ns->destroyer);
> +}
>  EXPORT_SYMBOL(free_user_ns);

  reply	other threads:[~2009-02-23 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 12:55 [PATCH] Fix recursive lock in free_uid()/free_user_ns() David Howells
2009-02-23 20:33 ` Serge E. Hallyn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-24 21:28 David Howells

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=20090223203356.GA30533@us.ibm.com \
    --to=serue@us.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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