From: Tomas Henzl <thenzl@redhat.com>
To: linux-scsi@vger.kernel.org
Cc: James Bottomley <James.Bottomley@suse.de>, Mike.Miller@hp.com
Subject: [PATCH][resubmit] cciss: fix spinlock use
Date: Fri, 26 Feb 2010 15:39:11 +0100 [thread overview]
Message-ID: <4B87DD0F.1060506@redhat.com> (raw)
This is a third attempt - it is already
acked by Mike Miller - http://article.gmane.org/gmane.linux.scsi/54492
fail_all_cmds is called from do_cciss_intr with spinlock acquired.
So when in an error-handling situation, fail_all_cmds() is called
it attempts to *reacquire* the lock.
This removes the spinlock lock/unlock from fail_all_cmds and adds a
spin_unlock after the call to fail_all_cmds before return.
Signed-off-by: Tomas Henzl <thenzl@redhat.com>
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index 873e594..0a3fce8 100644
--- a/drivers/block/cciss.c
+++ b/drivers/block/cciss.c
@@ -3298,6 +3298,7 @@ static irqreturn_t do_cciss_intr(int irq, void *dev_id)
"cciss: controller cciss%d failed, stopping.\n",
h->ctlr);
fail_all_cmds(h->ctlr);
+ spin_unlock_irqrestore(CCISS_LOCK(h->ctlr), flags);
return IRQ_HANDLED;
}
@@ -4553,8 +4554,6 @@ static void fail_all_cmds(unsigned long ctlr)
printk(KERN_WARNING "cciss%d: controller not responding.\n", h->ctlr);
h->alive = 0; /* the controller apparently died... */
- spin_lock_irqsave(CCISS_LOCK(ctlr), flags);
-
pci_disable_device(h->pdev); /* Make sure it is really dead. */
/* move everything off the request queue onto the completed queue */
@@ -4580,7 +4579,6 @@ static void fail_all_cmds(unsigned long ctlr)
complete_scsi_command(c, 0, 0);
#endif
}
- spin_unlock_irqrestore(CCISS_LOCK(ctlr), flags);
return;
}
reply other threads:[~2010-02-26 14:39 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=4B87DD0F.1060506@redhat.com \
--to=thenzl@redhat.com \
--cc=James.Bottomley@suse.de \
--cc=Mike.Miller@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