From: sashiko-bot@kernel.org
To: "Konstantin Taranov" <kotaranov@linux.microsoft.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next v5 10/10] RDMA/mana_ib: Drain kernel receive and send queues
Date: Sat, 17 Oct 2026 07:01:36 +0000 [thread overview]
Message-ID: <sashiko-outbox-175357@kernel.org> (raw)
In-Reply-To: <20261017064413.995985-11-kotaranov@linux.microsoft.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] RDMA/mana_ib: lost poll wakeup in mana_ib_drain_sq() and mana_ib_drain_rq()
--
commit cdad9731bfb8c6291bf5161e04f6798a87eaf888
Author: Konstantin Taranov <kotaranov@microsoft.com>
RDMA/mana_ib: Drain kernel receive and send queues
This commit implements the core drain_rq and drain_sq device operations for
mana_ib RC QPs by transitioning the QP to IB_QPS_ERR, posting a marker WR,
and waiting for its completion.
> diff --git a/drivers/infiniband/hw/mana/qp.c b/drivers/infiniband/hw/mana/qp.c
> index 04755bec015ed..8557453d39194 100644
> --- a/drivers/infiniband/hw/mana/qp.c
> +++ b/drivers/infiniband/hw/mana/qp.c
> @@ -1381,3 +1381,106 @@ int mana_ib_destroy_qp(struct ib_qp *ibqp, struct ib_udata *udata)
>
> return -ENOENT;
> }
> +
> +struct mana_ib_drain_cqe {
> + struct ib_cqe cqe;
> + struct completion done;
> +};
> +
> +static void mana_ib_drain_qp_done(struct ib_cq *cq, struct ib_wc *wc)
> +{
> + struct mana_ib_drain_cqe *cqe = container_of(wc->wr_cqe,
> + struct mana_ib_drain_cqe,
> + cqe);
> + complete(&cqe->done);
> +}
> +
> +void mana_ib_drain_sq(struct ib_qp *ibqp)
> +{
> + struct ib_qp_attr attr = { .qp_state = IB_QPS_ERR };
> + struct mana_ib_drain_cqe sdrain;
> + struct ib_rdma_wr swr = {
> + .wr = {
> + .next = NULL,
> + .wr_cqe = &sdrain.cqe,
> + .opcode = IB_WR_SEND,
> + },
> + };
> + const struct ib_send_wr *bad_swr;
> + struct ib_cq *cq = ibqp->send_cq;
> + int ret;
> +
> + if (ibqp->qp_type != IB_QPT_RC) {
> + ibdev_err(ibqp->device, "SQ drain is only supported for RC QPs (type %u)\n",
> + ibqp->qp_type);
> + return;
> + }
> +
> + ret = ib_modify_qp(ibqp, &attr, IB_QP_STATE);
> + if (ret) {
> + ibdev_err(ibqp->device, "Failed to drain SQ: modify QP returned %d\n", ret);
> + return;
> + }
> +
> + sdrain.cqe.done = mana_ib_drain_qp_done;
> + init_completion(&sdrain.done);
> +
> + ret = ib_post_send(ibqp, &swr.wr, &bad_swr);
> + if (ret) {
> + ibdev_err(ibqp->device, "Failed to post SQ drain WR: %d\n", ret);
> + return;
> + }
> +
> + if (cq->poll_ctx != IB_POLL_DIRECT && cq->comp_handler)
> + cq->comp_handler(cq, cq->cq_context);
> +
> + if (cq->poll_ctx == IB_POLL_DIRECT) {
> + while (!wait_for_completion_timeout(&sdrain.done, HZ / 10))
> + ib_process_cq_direct(cq, -1);
> + } else {
> + wait_for_completion(&sdrain.done);
> + }
> +}
> +
> +void mana_ib_drain_rq(struct ib_qp *ibqp)
> +{
> + struct ib_qp_attr attr = { .qp_state = IB_QPS_ERR };
> + struct mana_ib_drain_cqe rdrain;
> + struct ib_recv_wr rwr = {
> + .next = NULL,
> + .wr_cqe = &rdrain.cqe,
> + };
> + struct ib_cq *cq = ibqp->recv_cq;
> + int ret;
> +
> + if (ibqp->qp_type != IB_QPT_RC) {
> + ibdev_err(ibqp->device, "RQ drain is only supported for RC QPs (type %u)\n",
> + ibqp->qp_type);
> + return;
> + }
> +
> + ret = ib_modify_qp(ibqp, &attr, IB_QP_STATE);
> + if (ret) {
> + ibdev_err(ibqp->device, "Failed to drain RQ: modify QP returned %d\n", ret);
> + return;
> + }
> +
> + rdrain.cqe.done = mana_ib_drain_qp_done;
> + init_completion(&rdrain.done);
> +
> + ret = ib_post_recv(ibqp, &rwr, NULL);
> + if (ret) {
> + ibdev_err(ibqp->device, "Failed to post RQ drain WR: %d\n", ret);
> + return;
> + }
> +
> + if (cq->poll_ctx != IB_POLL_DIRECT && cq->comp_handler)
> + cq->comp_handler(cq, cq->cq_context);
> +
> + if (cq->poll_ctx == IB_POLL_DIRECT) {
> + while (!wait_for_completion_timeout(&rdrain.done, HZ / 10))
> + ib_process_cq_direct(cq, -1);
> + } else {
> + wait_for_completion(&rdrain.done);
> + }
> +}
[Severity: High]
Can mana_ib_drain_sq() and mana_ib_drain_rq() lose a wakeup and hang in
wait_for_completion() when cq->poll_ctx is IB_POLL_SOFTIRQ?
In mana_ib_drain_sq() and mana_ib_drain_rq(), ib_modify_qp() transitions
the QP to IB_QPS_ERR before the drain WR is posted. Inside
mana_ib_modify_qp(), mana_add_qp_to_error_cqs() adds the QP to the CQ error
lists and mana_ib_notify_error_cqs() immediately calls cq->comp_handler():
drivers/infiniband/hw/mana/qp.c:mana_ib_notify_error_cqs() {
if (send_cq->poll_ctx != IB_POLL_DIRECT && send_cq->comp_handler)
send_cq->comp_handler(send_cq, send_cq->cq_context);
if (recv_cq != send_cq && recv_cq->poll_ctx != IB_POLL_DIRECT &&
recv_cq->comp_handler)
recv_cq->comp_handler(recv_cq, recv_cq->cq_context);
}
For IB_POLL_SOFTIRQ, cq->comp_handler is ib_cq_completion_softirq(), which
calls irq_poll_sched(&cq->iop), setting IRQ_POLL_F_SCHED and scheduling
ib_poll_handler():
drivers/infiniband/core/cq.c:ib_poll_handler() {
completed = __ib_process_cq(cq, budget, cq->wc, IB_POLL_BATCH);
if (completed < budget) {
irq_poll_complete(&cq->iop);
if (ib_req_notify_cq(cq, IB_POLL_FLAGS) > 0) {
trace_cq_reschedule(cq);
irq_poll_sched(&cq->iop);
}
}
...
}
In __ib_process_cq(), mana_ib_poll_cq() takes cq->cq_lock, polls hardware
CQEs, calls mana_flush_completions() for currently queued shadow WQEs, and
releases cq->cq_lock. __ib_process_cq() then invokes wc->wr_cqe->done() for
those flushed entries while IRQ_POLL_F_SCHED is still set.
Also, during ib_drain_qp() when send_cq == recv_cq, mana_flush_completions()
flushes both send_err_qp_list (including sdrain) and recv_err_qp_list in a
single mana_ib_poll_cq() call; __ib_process_cq() invokes sdrain.cqe.done()
on the first WC while still iterating through the remaining flushed RQ WCs
with IRQ_POLL_F_SCHED set, waking the caller to immediately enter
mana_ib_drain_rq().
If mana_ib_drain_sq() or mana_ib_drain_rq() posts its drain WR into
shadow_sq or shadow_rq after mana_ib_poll_cq() drops cq->cq_lock and then
calls cq->comp_handler() -> irq_poll_sched(&cq->iop) before
ib_poll_handler() reaches irq_poll_complete(&cq->iop), irq_poll_sched() sees
IRQ_POLL_F_SCHED is already set and returns as a no-op.
When ib_poll_handler() then calls irq_poll_complete(&cq->iop) followed by
ib_req_notify_cq(cq, IB_POLL_FLAGS) -> mana_ib_arm_cq(), mana_ib_arm_cq()
only checks cq->has_pending_cqe:
drivers/infiniband/hw/mana/cq.c:mana_ib_arm_cq() {
spin_lock_irqsave(&cq->cq_lock, irq_flags);
mana_ib_cq_doorbell(cq, SET_ARM_BIT);
if (flags & IB_CQ_REPORT_MISSED_EVENTS)
missed = cq->has_pending_cqe;
spin_unlock_irqrestore(&cq->cq_lock, irq_flags);
return missed;
}
Because mana_ib_arm_cq() does not check for unconsumed software-flushed
shadow WQEs on send_err_qp_list or recv_err_qp_list and the QP in
IB_QPS_ERR will not produce hardware CQEs for the drain WR,
mana_ib_arm_cq() returns 0 and cq->iop is never rescheduled.
Should this synchronize with the softirq poll context using
irq_poll_disable(&cq->iop) and irq_poll_enable(&cq->iop) when invoking the
completion handler (similar to mlx4, mlx5, and hns), or report pending
error QP shadow WQEs in mana_ib_arm_cq()?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261017064413.995985-1-kotaranov@linux.microsoft.com?part=10
prev parent reply other threads:[~2026-10-17 7:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 6:44 [PATCH rdma-next v5 00/10] RDMA/mana_ib: Add kernel RC and fast registration support Konstantin Taranov
2026-10-17 6:44 ` [PATCH rdma-next v5 01/10] RDMA/mana_ib: Allocate and map fast-registration MRs Konstantin Taranov
2026-10-17 6:49 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 02/10] RDMA/mana: Create and destroy kernel RC QPs Konstantin Taranov
2026-10-17 6:52 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 03/10] net/mana: Extend GDMA encoding for new RDMA WQEs Konstantin Taranov
2026-10-17 6:54 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 04/10] RDMA/mana_ib: Maintain kernel RC QP state Konstantin Taranov
2026-10-17 6:48 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 05/10] RDMA/mana_ib: Post receive WRs on kernel RC QPs Konstantin Taranov
2026-10-17 6:48 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 06/10] RDMA/mana_ib: Post send and memory-management WRs on " Konstantin Taranov
2026-10-17 7:00 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 07/10] RDMA/mana_ib: Poll RC completions using PSN and FSN progress Konstantin Taranov
2026-10-17 6:56 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 08/10] RDMA/mana_ib: Flush and notify CQs when kernel QPs enter ERR Konstantin Taranov
2026-10-17 7:12 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 09/10] RDMA/mana_ib: Handle error CQEs for RC QPs Konstantin Taranov
2026-10-17 7:23 ` sashiko-bot
2026-10-17 6:44 ` [PATCH rdma-next v5 10/10] RDMA/mana_ib: Drain kernel receive and send queues Konstantin Taranov
2026-10-17 7:01 ` sashiko-bot [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=sashiko-outbox-175357@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kotaranov@linux.microsoft.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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