From: Dan Carpenter <dan.carpenter@oracle.com>
To: santoshprasadnayak@gmail.com
Cc: Jack Wang <jack_wang@usish.com>, linux-scsi@vger.kernel.org
Subject: re: [SCSI] pm8001: Fix bogus interrupt state flag issue.
Date: Thu, 1 Mar 2012 17:22:25 +0300 [thread overview]
Message-ID: <20120301142225.GA9789@elgon.mountain> (raw)
Hello Santosh Nayak,
The patch bdaefbf580cd: "[SCSI] pm8001: Fix bogus interrupt state
flag issue." from Feb 26, 2012, leads to the following warning:
drivers/scsi/pm8001/pm8001_hwi.c:2400 mpi_sata_completion()
error: double unlock 'irq:'
} else if (t->uldd_task) {
- spin_unlock_irqrestore(&t->task_state_lock, flags);
+ spin_unlock_irq(&t->task_state_lock);
^^^^^^^^^^^^^^^
pm8001_ccb_task_free(pm8001_ha, t, ccb, tag);
mb();/* ditto */
- spin_unlock_irqrestore(&pm8001_ha->lock, flags);
+ spin_unlock_irq(&pm8001_ha->lock);
^^^^^^^^^^^^^^^
It doesn't make sense to enable IRQs twice. I'm not sure if it should
be the first or second unlock which enables them.
t->task_done(t);
- spin_lock_irqsave(&pm8001_ha->lock, flags);
+ spin_lock_irq(&pm8001_ha->lock);
} else if (!t->uldd_task) {
- spin_unlock_irqrestore(&t->task_state_lock, flags);
+ spin_unlock_irq(&t->task_state_lock);
^^^^^^^^^^^^^^^
pm8001_ccb_task_free(pm8001_ha, t, ccb, tag);
mb();/*ditto*/
- spin_unlock_irqrestore(&pm8001_ha->lock, flags);
+ spin_unlock_irq(&pm8001_ha->lock);
^^^^^^^^^^^^^^^
Same thing again.
t->task_done(t);
- spin_lock_irqsave(&pm8001_ha->lock, flags);
+ spin_lock_irq(&pm8001_ha->lock);
}
regards,
dan carpenter
next reply other threads:[~2012-03-01 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 14:22 Dan Carpenter [this message]
2012-03-01 14:24 ` [SCSI] pm8001: Fix bogus interrupt state flag issue santosh prasad nayak
2012-03-01 14:37 ` Dan Carpenter
2012-03-01 14:41 ` santosh prasad nayak
2012-03-02 1:06 ` Jack Wang
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=20120301142225.GA9789@elgon.mountain \
--to=dan.carpenter@oracle.com \
--cc=jack_wang@usish.com \
--cc=linux-scsi@vger.kernel.org \
--cc=santoshprasadnayak@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.