From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>
Subject: Re: [patch, lock validator] fix uidhash_lock <-> RCU deadlock
Date: Wed, 25 Jan 2006 08:59:37 -0800 [thread overview]
Message-ID: <1138208378.3992.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20060125142307.GA5427@elte.hu>
On Wed, 2006-01-25 at 15:23 +0100, Ingo Molnar wrote:
> RCU task-struct freeing can call free_uid(), which is taking
> uidhash_lock - while other users of uidhash_lock are softirq-unsafe.
>
> This bug was found by the lock validator i'm working on:
What is it doing exactly ?
Daniel
next prev parent reply other threads:[~2006-01-25 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 14:23 [patch, lock validator] fix uidhash_lock <-> RCU deadlock Ingo Molnar
2006-01-25 16:59 ` Daniel Walker [this message]
2006-01-29 13:55 ` Ingo Molnar
2006-01-26 11:13 ` Paul E. McKenney
2006-01-28 0:22 ` Linus Torvalds
2006-01-28 2:40 ` Paul E. McKenney
2006-01-30 4:14 ` Paul E. McKenney
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=1138208378.3992.7.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=torvalds@osdl.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