From: Logan Gunthorpe <logang@deltatee.com>
To: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>
Cc: Frank Li <Frank.li@nxp.com>,
Logan Gunthorpe <logang@deltatee.com>,
Sashiko <sashiko-bot@kernel.org>
Subject: [PATCH v2 6/6] dmaengine: plx_dma: don't invoke client callbacks with ring_lock held
Date: Tue, 10 Nov 2026 11:39:27 -0600 [thread overview]
Message-ID: <20261110173927.624629-7-logang@deltatee.com> (raw)
In-Reply-To: <20261110173927.624629-1-logang@deltatee.com>
plx_dma_process_desc() and plx_dma_abort_desc() invoke the client's
completion callback with ring_lock held. A callback that submits a new
transfer, which is common, deadlocks taking the same lock in
plx_dma_prep_memcpy().
Copy and clear the callback and advance tail under ring_lock, then drop
it to invoke the callback. To keep callbacks in order and ensure
plx_dma_free_chan_resources() can't return while one is still running
from plx_dma_remove(), serialize completion with a new complete_lock
held across the whole loop. plx_dma_tx_status() only trylocks it, so a
callback that polls the channel won't deadlock.
Reported-by: Sashiko <sashiko-bot@kernel.org>
Link: https://lore.kernel.org/dmaengine/20260717223217.B6FBF1F000E9@smtp.kernel.org
Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
---
drivers/dma/plx_dma.c | 45 ++++++++++++++++++++++++++++++++++++-------
1 file changed, 38 insertions(+), 7 deletions(-)
diff --git a/drivers/dma/plx_dma.c b/drivers/dma/plx_dma.c
index d1bdff1b7310..394ca5483434 100644
--- a/drivers/dma/plx_dma.c
+++ b/drivers/dma/plx_dma.c
@@ -108,6 +108,8 @@ struct plx_dma_dev {
void __iomem *bar;
struct tasklet_struct desc_task;
+ /* serializes descriptor completion and callback invocation */
+ spinlock_t complete_lock;
spinlock_t ring_lock;
bool ring_active;
int head;
@@ -132,12 +134,15 @@ static struct plx_dma_desc *plx_dma_get_desc(struct plx_dma_dev *plxdev, int i)
return plxdev->desc_ring[i & (PLX_DMA_RING_COUNT - 1)];
}
-static void plx_dma_process_desc(struct plx_dma_dev *plxdev)
+static void plx_dma_process_desc_unlocked(struct plx_dma_dev *plxdev)
{
+ struct dmaengine_desc_callback cb;
struct dmaengine_result res;
struct plx_dma_desc *desc;
u32 flags;
+ lockdep_assert_held(&plxdev->complete_lock);
+
spin_lock_bh(&plxdev->ring_lock);
while (plxdev->tail != plxdev->head) {
@@ -166,22 +171,35 @@ static void plx_dma_process_desc(struct plx_dma_dev *plxdev)
dma_cookie_complete(&desc->txd);
dma_descriptor_unmap(&desc->txd);
- dmaengine_desc_get_callback_invoke(&desc->txd, &res);
+ dmaengine_desc_get_callback(&desc->txd, &cb);
desc->txd.callback = NULL;
desc->txd.callback_result = NULL;
-
plxdev->tail++;
+
+ spin_unlock_bh(&plxdev->ring_lock);
+ dmaengine_desc_callback_invoke(&cb, &res);
+ spin_lock_bh(&plxdev->ring_lock);
}
spin_unlock_bh(&plxdev->ring_lock);
}
+static void plx_dma_process_desc(struct plx_dma_dev *plxdev)
+{
+ spin_lock_bh(&plxdev->complete_lock);
+ plx_dma_process_desc_unlocked(plxdev);
+ spin_unlock_bh(&plxdev->complete_lock);
+}
+
static void plx_dma_abort_desc(struct plx_dma_dev *plxdev)
{
+ struct dmaengine_desc_callback cb;
struct dmaengine_result res;
struct plx_dma_desc *desc;
- plx_dma_process_desc(plxdev);
+ spin_lock_bh(&plxdev->complete_lock);
+
+ plx_dma_process_desc_unlocked(plxdev);
spin_lock_bh(&plxdev->ring_lock);
@@ -193,14 +211,18 @@ static void plx_dma_abort_desc(struct plx_dma_dev *plxdev)
dma_cookie_complete(&desc->txd);
dma_descriptor_unmap(&desc->txd);
- dmaengine_desc_get_callback_invoke(&desc->txd, &res);
+ dmaengine_desc_get_callback(&desc->txd, &cb);
desc->txd.callback = NULL;
desc->txd.callback_result = NULL;
-
plxdev->tail++;
+
+ spin_unlock_bh(&plxdev->ring_lock);
+ dmaengine_desc_callback_invoke(&cb, &res);
+ spin_lock_bh(&plxdev->ring_lock);
}
spin_unlock_bh(&plxdev->ring_lock);
+ spin_unlock_bh(&plxdev->complete_lock);
}
static void __plx_dma_stop(struct plx_dma_dev *plxdev)
@@ -337,7 +359,15 @@ static enum dma_status plx_dma_tx_status(struct dma_chan *chan,
if (ret == DMA_COMPLETE)
return ret;
- plx_dma_process_desc(plxdev);
+ /*
+ * If another context is already completing descriptors (possibly
+ * a callback on this CPU that is polling the channel), let it
+ * finish rather than waiting on it.
+ */
+ if (spin_trylock_bh(&plxdev->complete_lock)) {
+ plx_dma_process_desc_unlocked(plxdev);
+ spin_unlock_bh(&plxdev->complete_lock);
+ }
return dma_cookie_status(chan, cookie, txstate);
}
@@ -518,6 +548,7 @@ static int plx_dma_create(struct pci_dev *pdev)
if (!plxdev)
return -ENOMEM;
+ spin_lock_init(&plxdev->complete_lock);
spin_lock_init(&plxdev->ring_lock);
tasklet_setup(&plxdev->desc_task, plx_dma_desc_task);
--
2.47.3
prev parent reply other threads:[~2026-11-10 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 17:39 [PATCH v2 0/6] plx_dma fixes Logan Gunthorpe
2026-11-10 17:39 ` [PATCH v2 1/6] dmaengine: plx_dma: don't call pci_irq_vector() under rcu_read_lock() Logan Gunthorpe
2026-11-10 17:39 ` [PATCH v2 2/6] dmaengine: plx_dma: fix descriptor ring leak in alloc_chan_resources() Logan Gunthorpe
2026-11-10 17:39 ` [PATCH v2 3/6] dmaengine: plx_dma: use writel() for the 32-bit PLX_REG_CTRL register Logan Gunthorpe
2026-11-10 17:39 ` [PATCH v2 4/6] dmaengine: plx_dma: add dma_rmb() after observing write-back status Logan Gunthorpe
2026-11-10 17:39 ` [PATCH v2 5/6] dmaengine: plx_dma: use spin_lock_bh() in plx_dma_process_desc() Logan Gunthorpe
2026-11-10 17:39 ` Logan Gunthorpe [this message]
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=20261110173927.624629-7-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=Frank.li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®