From: "Serge E. Hallyn" <serue@us.ibm.com>
To: David Howells <dhowells@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Subject: Re: [CRED bug?] 2.6.29-rc3 don't survive on stress workload
Date: Thu, 12 Feb 2009 08:39:32 -0600 [thread overview]
Message-ID: <20090212143932.GA10101@us.ibm.com> (raw)
In-Reply-To: <27547.1234440246@redhat.com>
Quoting David Howells (dhowells@redhat.com):
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
> > but perhaps I am merely lucky guy.
>
> Or perhaps Serge's patch fixes it - as I said I don't have it applied - though
> I don't see exactly why it should fix this problem...
I believe it was because
1. put_user_ns() was being called before the uid (which
was in the init_user_ns) was unhashed
2. alloc_uid would race in before the unhash, find
the hashed uid, and reuse it - without doing
another get_user_ns().
so a reference was lost.
-serge
next prev parent reply other threads:[~2009-02-12 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 5:41 [CRED bug?] 2.6.29-rc3 don't survive on stress workload KOSAKI Motohiro
2009-02-10 7:10 ` Vegard Nossum
2009-02-10 7:28 ` KOSAKI Motohiro
2009-02-11 3:56 ` Vegard Nossum
2009-02-11 10:48 ` David Howells
2009-02-10 12:18 ` Ingo Molnar
2009-02-11 12:25 ` KOSAKI Motohiro
2009-02-11 12:54 ` David Howells
2009-02-10 10:35 ` David Howells
2009-02-10 10:49 ` KOSAKI Motohiro
2009-02-11 12:41 ` David Howells
2009-02-11 12:52 ` KOSAKI Motohiro
2009-02-11 13:09 ` David Howells
2009-02-11 14:04 ` KOSAKI Motohiro
2009-02-11 16:33 ` Ingo Molnar
2009-02-11 17:07 ` David Howells
2009-02-11 17:19 ` Ingo Molnar
2009-02-12 11:09 ` David Howells
2009-02-12 11:23 ` KOSAKI Motohiro
2009-02-12 12:04 ` David Howells
2009-02-12 14:39 ` Serge E. Hallyn [this message]
2009-02-12 17:18 ` David Howells
2009-02-13 4:44 ` KOSAKI Motohiro
2009-02-13 8:28 ` Ingo Molnar
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=20090212143932.GA10101@us.ibm.com \
--to=serue@us.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=dhowells@redhat.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
/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