From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: gaash-ppclnx@gaashh.com
Cc: linuxppc-dev@ozlabs.org, Gilad Ben-Yossef <gilad@codefidence.com>
Subject: Re: mmu_hash_lock deadlock causes kernel stuck at 2.6.21 SMP powerpc 32bit
Date: Mon, 31 Mar 2008 08:40:21 +1100 [thread overview]
Message-ID: <1206913221.10388.125.camel@pasglop> (raw)
In-Reply-To: <90380.16819.qm@web39603.mail.mud.yahoo.com>
On Sun, 2008-03-30 at 14:28 -0700, Gaash Hazan wrote:
> To verify the theory, hash_page_sync() was wrapped
> with interrupts disabled code and problem never
> occurred again. Of course this is temporary workaround
> as there are several places needed to be fixed.
It is definitely a bug in hash_page_sync() which should
clear MSR:EE while holding the lock.
I'll do a patch.
Thanks for finding that out !
Cheers,
Ben.
next prev parent reply other threads:[~2008-03-30 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 21:28 mmu_hash_lock deadlock causes kernel stuck at 2.6.21 SMP powerpc 32bit Gaash Hazan
2008-03-30 21:40 ` Benjamin Herrenschmidt [this message]
2008-03-30 21:49 ` [PATCH] powerpc: Fix deadlock with mmu_hash_lock in hash_page_sync Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 11:47 mmu_hash_lock deadlock causes kernel stuck at 2.6.21 SMP powerpc 32bit Gaash Hazan
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=1206913221.10388.125.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=gaash-ppclnx@gaashh.com \
--cc=gilad@codefidence.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).