mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, ryan <ryan@netidea.com>,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: Kernel 2.4.0test10 crash (RAID+SMP)
Date: Mon, 6 Nov 2000 01:40:09 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10011060138320.14903-100000@master.linux-ide.org> (raw)
In-Reply-To: <3A067318.E9C6ADDF@mandrakesoft.com>

On Mon, 6 Nov 2000, Jeff Garzik wrote:

> Neil Brown wrote:
> > It looks like an interupt is happening while another interrupt is
> > happening, which should be impossible... but it isn't.
> 
> If multiple interrupts are hitting a single code path (like IDE irqs 14
> -and- 15), you definitely have to think about that.  The reentrancy
> guarantee only exists when a single IRQ is assigned to a single
> handler...
Jeff,

This is likely the classic case where the driver hangs on to the global
lock way to lock because it is grabbed to early wrt what I am changing the
behavior to...

Cheers,

Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-06  9:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 21:08 ryan
2000-11-06  0:04 ` Keith Owens
2000-11-06  1:39   ` ryan
2000-11-06  3:12     ` Neil Brown
2000-11-06  0:09       ` ryan
2000-11-06  9:00       ` Jeff Garzik
2000-11-06  9:40         ` Andre Hedrick [this message]
2000-11-06 22:19         ` Neil Brown
2000-11-06 11:51 ` Jason Straight
2000-11-07  0:02 Ion Badulescu

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=Pine.LNX.4.10.10011060138320.14903-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=ryan@netidea.com \
    /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

all inboxes | Powered by JetHome®