From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rdma_rxe: call comp_handler without holding cq->cq_lock
Date: Mon, 18 Aug 2025 19:37:16 -0700 [thread overview]
Message-ID: <e0f88ef5-b046-4128-8c81-ce3c7e20274c@linux.dev> (raw)
In-Reply-To: <20250806123921.633410-1-philipp.reisner@linbit.com>
在 2025/8/6 5:39, Philipp Reisner 写道:
> 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->cw_lock.
>
> Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com>
> ---
> drivers/infiniband/sw/rxe/rxe_cq.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_cq.c b/drivers/infiniband/sw/rxe/rxe_cq.c
> index fffd144d509e..1195e109f89b 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;
> + u8 notify;
>
> spin_lock_irqsave(&cq->cq_lock, flags);
>
> @@ -110,14 +111,15 @@ int rxe_cq_post(struct rxe_cq *cq, struct rxe_cqe *cqe, int solicited)
>
> queue_advance_producer(cq->queue, QUEUE_TYPE_TO_CLIENT);
>
> - 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);
> - }
> + notify = cq->notify;
> + cq->notify = 0;
Thanks a lot. In the original source code, cq->notify is set to 0 in the
following test cases:
if ((cq->notify & IB_CQ_NEXT_COMP) ||
(cq->notify & IB_CQ_SOLICITED && solicited))
but in your commit, the above test case is removed.
I am not sure if this will introduce any risk or not.
I am fine with others.
Reviewed-by: Zhu Yanjun <yanjun.zhu@linux.dev>
Zhu Yanjun
>
> spin_unlock_irqrestore(&cq->cq_lock, flags);
>
> + if ((notify & IB_CQ_NEXT_COMP) ||
> + (notify & IB_CQ_SOLICITED && solicited))
> + cq->ibcq.comp_handler(&cq->ibcq, cq->ibcq.cq_context);
> +
> return 0;
> }
>
next prev parent reply other threads:[~2025-08-19 2:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 12:39 [PATCH] rdma_rxe: call comp_handler without holding cq->cq_lock 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 [this message]
2025-08-19 17:24 ` Philipp Reisner
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=e0f88ef5-b046-4128-8c81-ce3c7e20274c@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.