From: Chengfeng Ye <dg573847474@gmail.com>
To: aacraid@microsemi.com, jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Chengfeng Ye <dg573847474@gmail.com>
Subject: [PATCH] scsi: ips: Fix potential deadlock on host->host_lock
Date: Tue, 26 Sep 2023 11:03:41 +0000 [thread overview]
Message-ID: <20230926110341.12028-1-dg573847474@gmail.com> (raw)
Hard interrupt do_ipsintr() could introduce double locks on
host->host_lock.
<Deadlock #1>
ips_eh_abort()
--> spin_loc(host->host_lock)
<interrupt>
--> do_ipsintr()
--> spin_lock(host->host_lock)
This flaw was found by an experimental static analysis tool I am
developing for irq-related deadlock.
To prevent the potential deadlock, the patch use spin_lock_irqsave()
on host->host_lock.
Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
---
drivers/scsi/ips.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/ips.c b/drivers/scsi/ips.c
index bb206509265e..3caab8233d68 100644
--- a/drivers/scsi/ips.c
+++ b/drivers/scsi/ips.c
@@ -776,6 +776,8 @@ int ips_eh_abort(struct scsi_cmnd *SC)
{
ips_ha_t *ha;
ips_copp_wait_item_t *item;
+ unsigned long flags;
+
int ret;
struct Scsi_Host *host;
@@ -793,7 +795,7 @@ int ips_eh_abort(struct scsi_cmnd *SC)
if (!ha->active)
return (FAILED);
- spin_lock(host->host_lock);
+ spin_lock_irqsave(host->host_lock, flags);
/* See if the command is on the copp queue */
item = ha->copp_waitlist.head;
@@ -814,7 +816,7 @@ int ips_eh_abort(struct scsi_cmnd *SC)
ret = (FAILED);
}
- spin_unlock(host->host_lock);
+ spin_unlock_irqrestore(host->host_lock, flags);
return ret;
}
--
2.17.1
reply other threads:[~2023-09-26 11:03 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=20230926110341.12028-1-dg573847474@gmail.com \
--to=dg573847474@gmail.com \
--cc=aacraid@microsemi.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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®