From: Leon Romanovsky <leon@kernel.org>
To: Chengfeng Ye <dg573847474@gmail.com>
Cc: dennis.dalessandro@cornelisnetworks.com, jgg@ziepe.ca,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IB/hfi1: Fix potential deadlock on &sde->flushlist_lock
Date: Tue, 4 Jul 2023 14:48:49 +0300 [thread overview]
Message-ID: <20230704114849.GA6455@unreal> (raw)
In-Reply-To: <20230628045925.5261-1-dg573847474@gmail.com>
On Wed, Jun 28, 2023 at 04:59:25AM +0000, Chengfeng Ye wrote:
> As &sde->flushlist_lock is acquired by timer sdma_err_progress_check()
> through layer of calls under softirq context, other process
> context code acquiring the lock should disable irq.
>
> Possible deadlock scenario
> sdma_send_txreq()
> -> spin_lock(&sde->flushlist_lock)
> <timer interrupt>
> -> sdma_err_progress_check()
> -> __sdma_process_event()
> -> sdma_set_state()
> -> sdma_flush()
> -> spin_lock_irqsave(&sde->flushlist_lock, flags) (deadlock here)
>
> This flaw was found using an experimental static analysis tool we are
> developing for irq-related deadlock.
>
> The tentative patch fix the potential deadlock by spin_lock_irqsave().
>
> Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
> ---
> drivers/infiniband/hw/hfi1/sdma.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/infiniband/hw/hfi1/sdma.c b/drivers/infiniband/hw/hfi1/sdma.c
> index bb2552dd29c1..0431f575c861 100644
> --- a/drivers/infiniband/hw/hfi1/sdma.c
> +++ b/drivers/infiniband/hw/hfi1/sdma.c
> @@ -2371,9 +2371,9 @@ int sdma_send_txreq(struct sdma_engine *sde,
> tx->sn = sde->tail_sn++;
> trace_hfi1_sdma_in_sn(sde, tx->sn);
> #endif
> - spin_lock(&sde->flushlist_lock);
> + spin_lock_irqsave(&sde->flushlist_lock, flags);
> list_add_tail(&tx->list, &sde->flushlist);
> - spin_unlock(&sde->flushlist_lock);
> + spin_unlock_irqrestore(&sde->flushlist_lock, flags);
> iowait_inc_wait_count(wait, tx->num_desc);
> queue_work_on(sde->cpu, system_highpri_wq, &sde->flush_worker);
> ret = -ECOMM;
It can't work as exactly after "ret = -ECOMM;" line, there is "goto unlock"
and there hfi1 calls to spin_unlock_irqrestore(..) with same "flags".
Plus, we already in context where interrupts are stopped.
Thanks
> @@ -2459,7 +2459,7 @@ int sdma_send_txlist(struct sdma_engine *sde, struct iowait_work *wait,
> *count_out = total_count;
> return ret;
> unlock_noconn:
> - spin_lock(&sde->flushlist_lock);
> + spin_lock_irqsave(&sde->flushlist_lock, flags);
> list_for_each_entry_safe(tx, tx_next, tx_list, list) {
> tx->wait = iowait_ioww_to_iow(wait);
> list_del_init(&tx->list);
> @@ -2472,7 +2472,7 @@ int sdma_send_txlist(struct sdma_engine *sde, struct iowait_work *wait,
> flush_count++;
> iowait_inc_wait_count(wait, tx->num_desc);
> }
> - spin_unlock(&sde->flushlist_lock);
> + spin_unlock_irqrestore(&sde->flushlist_lock, flags);
> queue_work_on(sde->cpu, system_highpri_wq, &sde->flush_worker);
> ret = -ECOMM;
> goto update_tail;
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-07-04 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 4:59 [PATCH] IB/hfi1: Fix potential deadlock on &sde->flushlist_lock Chengfeng Ye
2023-07-04 11:48 ` Leon Romanovsky [this message]
2023-07-04 17:42 ` Chengfeng Ye
2023-07-05 5:52 ` Leon Romanovsky
2023-07-05 6:47 ` Chengfeng Ye
2023-07-05 14:08 ` Dennis Dalessandro
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=20230704114849.GA6455@unreal \
--to=leon@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dg573847474@gmail.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@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