From: Logan Gunthorpe <logang@deltatee.com>
To: Chengfeng Ye <dg573847474@gmail.com>, vkoul@kernel.org
Cc: yuyunbo519@gmail.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, christophe.jaillet@wanadoo.fr
Subject: Re: [PATCH v2] dmaengine: plx_dma: Fix potential deadlock on &plxdev->ring_lock
Date: Sun, 30 Jul 2023 17:50:32 -0600 [thread overview]
Message-ID: <ff871e8d-c5b0-99ed-0a44-385d70c503c2@deltatee.com> (raw)
In-Reply-To: <20230729175952.4068-1-dg573847474@gmail.com>
On 7/29/23 11:59, Chengfeng Ye wrote:
> As plx_dma_process_desc() is invoked by both tasklet plx_dma_desc_task()
> under softirq context and plx_dma_tx_status() callback that executed under
> process context, the lock aquicision of &plxdev->ring_lock inside
> plx_dma_process_desc() should disable irq otherwise deadlock could happen
> if the irq preempts the execution of process context code while the lock
> is held in process context on the same CPU.
>
> Possible deadlock scenario:
> plx_dma_tx_status()
> -> plx_dma_process_desc()
> -> spin_lock(&plxdev->ring_lock)
> <tasklet softirq>
> -> plx_dma_desc_task()
> -> plx_dma_process_desc()
> -> spin_lock(&plxdev->ring_lock) (deadlock here)
>
> This flaw was found by an experimental static analysis tool I am developing
> for irq-related deadlock.
>
> The lock was changed from spin_lock_bh() to spin_lock() by a previous patch
> for performance concern but unintentionally brought this potential deadlock
> problem.
>
> This patch reverts back to spin_lock_bh() to fix the deadlock problem.
>
> Fixes: 1d05a0bdb420 ("dmaengine: plx_dma: Move spin_lock_bh() to spin_lock()")
> Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
>
Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
Thanks!
Logan
next prev parent reply other threads:[~2023-07-30 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 17:59 Chengfeng Ye
2023-07-30 23:50 ` Logan Gunthorpe [this message]
2023-08-28 16:18 ` Eric Schwarz
2023-08-29 3:10 ` Chengfeng Ye
2023-08-29 11:05 ` Eric Schwarz
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=ff871e8d-c5b0-99ed-0a44-385d70c503c2@deltatee.com \
--to=logang@deltatee.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dg573847474@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=yuyunbo519@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 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®