From: "Serge E. Hallyn" <serue@us.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Sesterhenn <snakebyte@gmx.de>,
containers@lists.osdl.org, linux-kernel@vger.kernel.org,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: namespaces?: bug at mm/slub.c:2750
Date: Wed, 11 Feb 2009 11:24:16 -0600 [thread overview]
Message-ID: <20090211172416.GA30756@us.ibm.com> (raw)
In-Reply-To: <1538.1234371764@redhat.com>
Quoting David Howells (dhowells@redhat.com):
> Serge E. Hallyn <serue@us.ibm.com> wrote:
>
> > static void uid_hash_remove(struct user_struct *up)
> > {
> > + put_user_ns(up->user_ns);
> > hlist_del_init(&up->uidhash_node);
> > }
>
> Don't you need to do the hlist_del_init() first? Otherwise, mightn't the
> put_user_ns() cause the namespace to be freed before hlist_del_init() removes
> the user_struct from it?
It's called under uidhash_lock spinlock so should be ok, but in
principle you're right so it's probably a good idea.
The main point is that without this patch, put_user_ns is done before
the hlist_del_init and *not* atomically under uidhash_lock.
thanks,
-serge
next prev parent reply other threads:[~2009-02-11 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 11:35 namespaces?: bug at mm/slub.c:2750 Eric Sesterhenn
2009-02-07 0:15 ` Andrew Morton
2009-02-09 11:53 ` Eric Sesterhenn
2009-02-11 7:55 ` Vegard Nossum
2009-02-11 8:07 ` Andrew Morton
2009-02-11 10:48 ` Vegard Nossum
2009-02-11 16:37 ` Serge E. Hallyn
2009-02-11 17:02 ` David Howells
2009-02-11 17:24 ` Serge E. Hallyn [this message]
2009-02-11 18:00 ` Vegard Nossum
2009-02-11 18:03 ` David Howells
2009-02-11 19:38 ` Serge E. Hallyn
2009-02-11 20:42 ` David Howells
2009-02-11 21:21 ` 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=20090211172416.GA30756@us.ibm.com \
--to=serue@us.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snakebyte@gmx.de \
--cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox