From: David Wilder <dwilder@us•ibm.com>
To: linuxppc-dev@ozlabs•org
Subject: might_sleep() called in die()
Date: Tue, 09 May 2006 14:28:47 -0700 [thread overview]
Message-ID: <4461098F.8050209@us.ibm.com> (raw)
Paul-
Can you advise me? In the die() function might_sleep() is called while
holding the die_lock (see call flow below).
If voluntary preemption is set this can cause a deadlock when multiple
Oops occur. I am seeing this problem when issuing a soft-reset as all
cups call die() at roughly the same time.
die()
->>show_regs()->>show_instructions()->>__get_user_nocheck()->>might_sleep()
My question is basically should die() ever call might_sleep()? If so why?
I currently working around the problem by calling clear_need_resched()
at the top of die().
--
David Wilder
IBM Linux Technology Center
Beaverton, Oregon, USA
dwilder@us•ibm.com
(503)578-3789
reply other threads:[~2006-05-09 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4461098F.8050209@us.ibm.com \
--to=dwilder@us$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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