From: Chengfeng Ye <dg573847474@gmail.com>
To: njavali@marvell.com, mrangankar@marvell.com,
GR-QLogic-Storage-Upstream@marvell.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] drbd: Fix potential deadlock on &session->back_lock and &session->frwd_lock
Date: Tue, 26 Sep 2023 11:00:18 +0000 [thread overview]
Message-ID: <20230926110018.11344-1-dg573847474@gmail.com> (raw)
Timer interrupt could introduce inverse lock ordering between
&session->frwd_lock and &session->back_lock if qedi_tmf_resp_work()
is interrupted by timer.
<Deadlock #1>
[CPU0] | [CPU1]
qedi_tmf_resp_work() |
--> spin_lock(&session->back_lock) |
| iscsi_eh_cmd_timed_out()
| --> spin_lock_bh(&session->frwd_lock)
|
| --> spin_lock(&session->back_lock)
<timer interrupt> |
--> iscsi_tmf_timedout() |
--> spin_lock(&session->frwd_lock) |
<Deadlock #2>
[CPU0] | [CPU1]
qedi_tmf_resp_work() |
--> __iscsi_complete_pdu() |
--> spin_lock(&conn->session->frwd_lock) |
| qedi_process_async_mesg()
| --> spin_lock_bh(&session->back_lock)
|
| --> __iscsi_complete_pdu()
| --> spin_lock(&conn->session->frwd_lock)
<timer interrupt> |
--> iscsi_check_transport_timeouts() |
--> iscsi_send_nopout() |
--> iscsi_alloc_mgmt_task() |
--> iscsi_put_task() |
--> spin_lock_bh(&session->back_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_bh()
on &session->back_lock inside qedi_tmf_resp_work() to prevent the
timer interrupts.
Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
---
drivers/scsi/qedi/qedi_fw.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/qedi/qedi_fw.c b/drivers/scsi/qedi/qedi_fw.c
index 6901738324da..60a168ca178c 100644
--- a/drivers/scsi/qedi/qedi_fw.c
+++ b/drivers/scsi/qedi/qedi_fw.c
@@ -162,9 +162,9 @@ static void qedi_tmf_resp_work(struct work_struct *work)
if (rval)
goto exit_tmf_resp;
- spin_lock(&session->back_lock);
+ spin_lock_bh(&session->back_lock);
__iscsi_complete_pdu(conn, (struct iscsi_hdr *)resp_hdr_ptr, NULL, 0);
- spin_unlock(&session->back_lock);
+ spin_unlock_bh(&session->back_lock);
exit_tmf_resp:
kfree(resp_hdr_ptr);
--
2.17.1
reply other threads:[~2023-09-26 11:00 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=20230926110018.11344-1-dg573847474@gmail.com \
--to=dg573847474@gmail.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mrangankar@marvell.com \
--cc=njavali@marvell.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®