From: Chengfeng Ye <dg573847474@gmail.com>
To: vkoul@kernel.org, allen.lkml@gmail.com, arnd@arndb.de,
christophe.jaillet@wanadoo.fr, yong.y.wang@intel.com
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Chengfeng Ye <dg573847474@gmail.com>
Subject: [PATCH] dmaengine: pch_dma: Fix potential deadlock on &pd_chan->lock
Date: Wed, 26 Jul 2023 06:23:13 +0000 [thread overview]
Message-ID: <20230726062313.77121-1-dg573847474@gmail.com> (raw)
As &pd_chan->lock is acquired by pdc_tasklet() under softirq context
scheduled by pd_irq(), other acquisition of the same lock under process
context should disable irq, otherwise deadlock could happen if the soft
irq preempts the execution of process context code while the lock is held
in process context on the same CPU.
pd_issue_pending(), pd_tx_submit(), pdc_desc_put() and pdc_desc_get() are
callbacks function or executed by callback functions that could execute
without irq disaled.
Possible deadlock scenario:
pd_prep_slave_sg()
-> pdc_desc_put()
-> spin_lock(&pd_chan->lock)
<tasklet softirq interruption>
-> pdc_tasklet()
-> spin_lock_irqsave(&pd_chan->lock, flags); (deadlock here)
This flaw was found by an experimental static analysis tool I am developing
for irq-related deadlock.
The tentative patch fixes the potential deadlock by spin_lock_irqsave() to
disable irq while lock is held.
Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
---
drivers/dma/pch_dma.c | 25 +++++++++++++++----------
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/dma/pch_dma.c b/drivers/dma/pch_dma.c
index c359decc07a3..ad9ac4f64961 100644
--- a/drivers/dma/pch_dma.c
+++ b/drivers/dma/pch_dma.c
@@ -409,8 +409,9 @@ static dma_cookie_t pd_tx_submit(struct dma_async_tx_descriptor *txd)
{
struct pch_dma_desc *desc = to_pd_desc(txd);
struct pch_dma_chan *pd_chan = to_pd_chan(txd->chan);
+ unsigned long flags;
- spin_lock(&pd_chan->lock);
+ spin_lock_irqsave(&pd_chan->lock, flags);
if (list_empty(&pd_chan->active_list)) {
list_add_tail(&desc->desc_node, &pd_chan->active_list);
@@ -419,7 +420,7 @@ static dma_cookie_t pd_tx_submit(struct dma_async_tx_descriptor *txd)
list_add_tail(&desc->desc_node, &pd_chan->queue);
}
- spin_unlock(&pd_chan->lock);
+ spin_unlock_irqrestore(&pd_chan->lock, flags);
return 0;
}
@@ -445,9 +446,10 @@ static struct pch_dma_desc *pdc_desc_get(struct pch_dma_chan *pd_chan)
{
struct pch_dma_desc *desc, *_d;
struct pch_dma_desc *ret = NULL;
+ unsigned long flags;
int i = 0;
- spin_lock(&pd_chan->lock);
+ spin_lock_irqsave(&pd_chan->lock, flags);
list_for_each_entry_safe(desc, _d, &pd_chan->free_list, desc_node) {
i++;
if (async_tx_test_ack(&desc->txd)) {
@@ -457,15 +459,15 @@ static struct pch_dma_desc *pdc_desc_get(struct pch_dma_chan *pd_chan)
}
dev_dbg(chan2dev(&pd_chan->chan), "desc %p not ACKed\n", desc);
}
- spin_unlock(&pd_chan->lock);
+ spin_unlock_irqrestore(&pd_chan->lock, flags);
dev_dbg(chan2dev(&pd_chan->chan), "scanned %d descriptors\n", i);
if (!ret) {
ret = pdc_alloc_desc(&pd_chan->chan, GFP_ATOMIC);
if (ret) {
- spin_lock(&pd_chan->lock);
+ spin_lock_irqsave(&pd_chan->lock, flags);
pd_chan->descs_allocated++;
- spin_unlock(&pd_chan->lock);
+ spin_unlock_irqrestore(&pd_chan->lock, flags);
} else {
dev_err(chan2dev(&pd_chan->chan),
"failed to alloc desc\n");
@@ -478,11 +480,13 @@ static struct pch_dma_desc *pdc_desc_get(struct pch_dma_chan *pd_chan)
static void pdc_desc_put(struct pch_dma_chan *pd_chan,
struct pch_dma_desc *desc)
{
+ unsigned long flags;
+
if (desc) {
- spin_lock(&pd_chan->lock);
+ spin_lock_irqsave(&pd_chan->lock, flags);
list_splice_init(&desc->tx_list, &pd_chan->free_list);
list_add(&desc->desc_node, &pd_chan->free_list);
- spin_unlock(&pd_chan->lock);
+ spin_unlock_irqrestore(&pd_chan->lock, flags);
}
}
@@ -555,11 +559,12 @@ static enum dma_status pd_tx_status(struct dma_chan *chan, dma_cookie_t cookie,
static void pd_issue_pending(struct dma_chan *chan)
{
struct pch_dma_chan *pd_chan = to_pd_chan(chan);
+ unsigned long flags;
if (pdc_is_idle(pd_chan)) {
- spin_lock(&pd_chan->lock);
+ spin_lock_irqsave(&pd_chan->lock, flags);
pdc_advance_work(pd_chan);
- spin_unlock(&pd_chan->lock);
+ spin_unlock_irqrestore(&pd_chan->lock, flags);
}
}
--
2.17.1
next reply other threads:[~2023-07-26 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 6:23 Chengfeng Ye [this message]
2023-08-16 17:03 ` Chengfeng Ye
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=20230726062313.77121-1-dg573847474@gmail.com \
--to=dg573847474@gmail.com \
--cc=allen.lkml@gmail.com \
--cc=arnd@arndb.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=yong.y.wang@intel.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®