From: Doug Ledford <dledford@redhat.com>
To: "Cameron, Steve" <Steve.Cameron@hp.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] 2.5.65, cciss_scsi, scsi error handling
Date: Tue, 18 Mar 2003 18:34:14 -0500 [thread overview]
Message-ID: <3E77ACF6.1000407@redhat.com> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E106404513385@cceexc18.americas.cpqcorp.net>
Cameron, Steve wrote:
> I think we can implement the abort and device reset handlers,
> (Seems like I tried this once before, but it got really ugly...
> Hmm, looking through my notes, I see this:
>
> me> Tue Jul 17 10:35:19 CDT 2001
> me> Actually, looking a bit harder, figured out the real problem
> me> was that the SCSI mid-layer's error processing code grabs the
> me> io_request_lock and disables interrupts before calling the
> me> driver's error handling routines. It holds the flags in a
> me> local variable inaccessible to the driver, so the driver
> me> cannot unlock and enable interrupts.
spin_unlock_irq(&hostptr->lock);
wait_for_interrupt();
spin_lock_irq(&hostptr->lock);
You don't need the variable because you already know that the interrupts
are off and you know you want them back off when you are done waiting.
So,t he irq variant of the spin lock functions will work just fine for you.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2003-03-18 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 23:22 [PATCH] 2.5.65, cciss_scsi, scsi error handling Cameron, Steve
2003-03-18 23:34 ` Doug Ledford [this message]
2003-03-19 20:32 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2003-03-18 10:06 Stephen Cameron
2003-03-18 22:13 ` James Bottomley
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=3E77ACF6.1000407@redhat.com \
--to=dledford@redhat.com \
--cc=James.Bottomley@steeleye.com \
--cc=Steve.Cameron@hp.com \
--cc=linux-scsi@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