From: Philipp Reisner <philipp.reisner@linbit.com>
To: yanjun.zhu@linux.dev
Cc: jgg@ziepe.ca, leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, philipp.reisner@linbit.com,
zyjzyj2000@gmail.com
Subject: [PATCH] rdma_rxe: call comp_handler without holding cq->cq_lock
Date: Tue, 19 Aug 2025 19:24:27 +0200 [thread overview]
Message-ID: <20250819172427.645153-1-philipp.reisner@linbit.com> (raw)
In-Reply-To: <e0f88ef5-b046-4128-8c81-ce3c7e20274c@linux.dev>
Allow the comp_handler callback implementation to call ib_poll_cq().
A call to ib_poll_cq() calls rxe_poll_cq() with the rdma_rxe driver.
And rxe_poll_cq() locks cq->cq_lock. That leads to a spinlock deadlock.
The Mellanox and Intel drivers allow a comp_handler callback
implementation to call ib_poll_cq().
Avoid the deadlock by calling the comp_handler callback without
holding cq->cq_lock.
Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
---
drivers/infiniband/sw/rxe/rxe_cq.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/sw/rxe/rxe_cq.c b/drivers/infiniband/sw/rxe/rxe_cq.c
index fffd144d509e..95652001665d 100644
--- a/drivers/infiniband/sw/rxe/rxe_cq.c
+++ b/drivers/infiniband/sw/rxe/rxe_cq.c
@@ -88,6 +88,7 @@ int rxe_cq_post(struct rxe_cq *cq, struct rxe_cqe *cqe, int solicited)
int full;
void *addr;
unsigned long flags;
+ bool invoke_handler = false;
spin_lock_irqsave(&cq->cq_lock, flags);
@@ -113,11 +114,14 @@ int rxe_cq_post(struct rxe_cq *cq, struct rxe_cqe *cqe, int solicited)
if ((cq->notify & IB_CQ_NEXT_COMP) ||
(cq->notify & IB_CQ_SOLICITED && solicited)) {
cq->notify = 0;
- cq->ibcq.comp_handler(&cq->ibcq, cq->ibcq.cq_context);
+ invoke_handler = true;
}
spin_unlock_irqrestore(&cq->cq_lock, flags);
+ if (invoke_handler)
+ cq->ibcq.comp_handler(&cq->ibcq, cq->ibcq.cq_context);
+
return 0;
}
--
2.50.1
next prev parent reply other threads:[~2025-08-19 17:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 12:39 Philipp Reisner
2025-08-07 1:09 ` Zhu Yanjun
2025-08-11 5:26 ` Philipp Reisner
2025-08-11 13:48 ` Zhu Yanjun
2025-08-12 15:54 ` Daisuke Matsuda
2025-08-14 5:33 ` Zhu Yanjun
2025-08-14 14:07 ` Daisuke Matsuda
[not found] ` <3cb43241-20d7-4ac9-b055-373fd058b3a3@linux.dev>
[not found] ` <2e645d1c-f853-4cee-9590-6f01820d027b@linux.dev>
2025-08-15 4:25 ` Zhu Yanjun
2025-08-15 18:29 ` Yanjun.Zhu
2025-08-16 15:57 ` Daisuke Matsuda
2025-08-19 2:37 ` Zhu Yanjun
2025-08-19 17:24 ` Philipp Reisner [this message]
2025-08-22 2:54 ` Zhu Yanjun
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=20250819172427.645153-1-philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
--cc=zyjzyj2000@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®