The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recursive deadlock on die_lock
Date: Sat, 13 Oct 2001 23:42:51 -0700	[thread overview]
Message-ID: <3BC933EA.4636D57C@zip.com.au> (raw)
In-Reply-To: <27496.1003033552@ocs3.intra.ocs.com.au>

Keith Owens wrote:
> 
> ...
> If show_registers() fails (which it does far too often on IA64) then
> the system deadlocks trying to recursively obtain die_lock.  Also
> die_lock is never used outside die(), it should be proc local.
> Suggested fix:
> 

Looks to me like it'll work.  But why does ia64 show_registers()
die so easily?  Can it be taught to validate addresses before
dereferencing them somehow?

  reply	other threads:[~2001-10-14  6:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14  4:25 Recursive deadlock on die_lock Keith Owens
2001-10-14  6:42 ` Andrew Morton [this message]
2001-10-14  7:13   ` Keith Owens
2001-10-14 23:14     ` Eric W. Biederman
2001-10-15  0:42       ` Keith Owens
     [not found] <fa.k3c2fuv.1q26ra4@ifi.uio.no>
     [not found] ` <fa.idkv82v.3jcuip@ifi.uio.no>
2001-10-15  1:55   ` Sam Varshavchik

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=3BC933EA.4636D57C@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=kaos@ocs.com.au \
    --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