From: Adrian Hunter <adrian.hunter@intel.com>
To: alexandre.belloni@bootlin.com
Cc: Frank.Li@nxp.com, linux-i3c@lists.infradead.org
Subject: [PATCH 05/12] i3c: mipi-i3c-hci: Fix race between DMA ring dequeue and the interrupt handler
Date: Fri, 27 Feb 2026 16:11:42 +0200 [thread overview]
Message-ID: <20260227141149.184980-6-adrian.hunter@intel.com> (raw)
In-Reply-To: <20260227141149.184980-1-adrian.hunter@intel.com>
The DMA ring bookkeeping in the MIPI I3C HCI driver is updated from two
contexts: the DMA ring dequeue path (hci_dma_dequeue_xfer()) and the
interrupt handler (hci_dma_xfer_done()). Both modify the ring’s
in‑flight transfer state - specifically rh->src_xfers[] and
xfer->ring_entry - but without any serialization. This allows the two
paths to race, potentially leading to inconsistent ring state.
Serialize access to the shared ring state by extending the existing ring
spinlock to cover the dequeue path and the relevant parts of the
interrupt handler. In the interrupt handler, clear the completed entry in
src_xfers[] so it cannot be matched or completed again.
Finally, place the ring restart sequence under the same lock in
hci_dma_dequeue_xfer() to avoid concurrent enqueue or completion
operations while the ring state is being modified.
Fixes: 9ad9a52cce282 ("i3c/master: introduce the mipi-i3c-hci driver")
Cc: stable@vger.kernel.org
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
---
drivers/i3c/master/mipi-i3c-hci/dma.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/i3c/master/mipi-i3c-hci/dma.c b/drivers/i3c/master/mipi-i3c-hci/dma.c
index 5a9af561e4cb..8d5f808e03ea 100644
--- a/drivers/i3c/master/mipi-i3c-hci/dma.c
+++ b/drivers/i3c/master/mipi-i3c-hci/dma.c
@@ -564,6 +564,8 @@ static bool hci_dma_dequeue_xfer(struct i3c_hci *hci,
WARN_ON(1);
}
+ spin_lock_irq(&rh->lock);
+
for (i = 0; i < n; i++) {
struct hci_xfer *xfer = xfer_list + i;
int idx = xfer->ring_entry;
@@ -597,6 +599,8 @@ static bool hci_dma_dequeue_xfer(struct i3c_hci *hci,
/* restart the ring */
rh_reg_write(RING_CONTROL, RING_CTRL_ENABLE);
+ spin_unlock_irq(&rh->lock);
+
return did_unqueue;
}
@@ -607,6 +611,8 @@ static void hci_dma_xfer_done(struct i3c_hci *hci, struct hci_rh_data *rh)
unsigned int done_cnt = 0;
struct hci_xfer *xfer;
+ spin_lock(&rh->lock);
+
for (;;) {
op2_val = rh_reg_read(RING_OPERATION2);
if (done_ptr == FIELD_GET(RING_OP2_CR_DEQ_PTR, op2_val))
@@ -622,6 +628,7 @@ static void hci_dma_xfer_done(struct i3c_hci *hci, struct hci_rh_data *rh)
dev_dbg(&hci->master.dev, "orphaned ring entry");
} else {
hci_dma_unmap_xfer(hci, xfer, 1);
+ rh->src_xfers[done_ptr] = NULL;
xfer->ring_entry = -1;
xfer->response = resp;
if (tid != xfer->cmd_tid) {
@@ -639,8 +646,6 @@ static void hci_dma_xfer_done(struct i3c_hci *hci, struct hci_rh_data *rh)
done_cnt += 1;
}
- /* take care to update the software dequeue pointer atomically */
- spin_lock(&rh->lock);
rh->xfer_space += done_cnt;
op1_val = rh_reg_read(RING_OPERATION1);
op1_val &= ~RING_OP1_CR_SW_DEQ_PTR;
--
2.51.0
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2026-02-27 14:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:11 [PATCH 00/12] i3c: mipi-i3c-hci: Fixes for v7.0 Adrian Hunter
2026-02-27 14:11 ` [PATCH 01/12] i3c: mipi-i3c-hci: Use ETIMEDOUT instead of ETIME for timeout errors Adrian Hunter
2026-02-27 16:00 ` Frank Li
2026-02-27 14:11 ` [PATCH 02/12] i3c: mipi-i3c-hci: Fix Hot-Join NACK Adrian Hunter
2026-02-27 16:03 ` Frank Li
2026-03-02 8:42 ` Adrian Hunter
2026-03-02 17:52 ` Frank Li
2026-02-27 14:11 ` [PATCH 03/12] i3c: mipi-i3c-hci: Fix race in DMA ring enqueue for parallel xfers Adrian Hunter
2026-02-27 16:09 ` Frank Li
2026-02-27 14:11 ` [PATCH 04/12] i3c: mipi-i3c-hci: Fix race in DMA ring dequeue Adrian Hunter
2026-02-27 16:18 ` Frank Li
2026-03-02 8:43 ` Adrian Hunter
2026-03-02 19:23 ` Frank Li
2026-03-04 17:58 ` Adrian Hunter
2026-02-27 14:11 ` Adrian Hunter [this message]
2026-02-27 16:21 ` [PATCH 05/12] i3c: mipi-i3c-hci: Fix race between DMA ring dequeue and the interrupt handler Frank Li
2026-02-27 14:11 ` [PATCH 06/12] i3c: mipi-i3c-hci: Correct RING_CTRL_ABORT handling in DMA dequeue Adrian Hunter
2026-02-27 16:25 ` Frank Li
2026-03-02 8:45 ` Adrian Hunter
2026-03-02 17:49 ` Frank Li
2026-02-27 14:11 ` [PATCH 07/12] i3c: mipi-i3c-hci: Add missing TID field to no-op command descriptor Adrian Hunter
2026-02-27 16:27 ` Frank Li
2026-02-27 14:11 ` [PATCH 08/12] i3c: mipi-i3c-hci: Restart DMA ring correctly after dequeue abort Adrian Hunter
2026-02-27 16:28 ` Frank Li
2026-02-27 14:11 ` [PATCH 09/12] i3c: mipi-i3c-hci: Consolidate common xfer processing logic Adrian Hunter
2026-02-27 16:30 ` Frank Li
2026-02-27 14:11 ` [PATCH 10/12] i3c: mipi-i3c-hci: Fix race in DMA error handling in interrupt context Adrian Hunter
2026-02-27 16:40 ` Frank Li
2026-03-02 8:45 ` Adrian Hunter
2026-02-27 14:11 ` [PATCH 11/12] i3c: mipi-i3c-hci: Fix handling of shared IRQs during early initialization Adrian Hunter
2026-02-27 16:42 ` Frank Li
2026-03-02 8:43 ` Adrian Hunter
2026-03-02 19:18 ` Frank Li
2026-03-04 18:13 ` Adrian Hunter
2026-02-27 14:11 ` [PATCH 12/12] i3c: mipi-i3c-hci: Fallback to software reset when bus disable fails Adrian Hunter
2026-02-27 16:44 ` Frank Li
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=20260227141149.184980-6-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.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