Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "David Hu" <dhu@x6u.co>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next 4/5] RDMA/irdma: Support UMEM attribute for CQ creation
Date: Sun, 11 Oct 2026 01:27:35 +0000	[thread overview]
Message-ID: <sashiko-outbox-166959@kernel.org> (raw)
In-Reply-To: <20261011011022.1445352-5-dhu@x6u.co>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] rdma/irdma: Memory and resource leak in irdma_resize_cq for 1-step CQs
--

commit fbc0fbebd82d8c5ffc02a6bcacb939600a040cd7
Author: David Hu <xuehaohu@google.com>

RDMA/irdma: Support UMEM attribute for CQ creation

This patch supports the standard 1-step queue buffer creation model for CQs
using UMEM attributes. It sets up hardware PBLs directly from the pinned CQ
and shadow umems, and adds proper cleanup in irdma_cq_free_rsrc() upon CQ
destruction. Legacy 2-step registration is maintained for backward
compatibility.

> diff --git a/drivers/infiniband/hw/irdma/verbs.c b/drivers/infiniband/hw/irdma/verbs.c
> index ab25445f38282..e4a02a6b2a113 100644
> --- a/drivers/infiniband/hw/irdma/verbs.c
> +++ b/drivers/infiniband/hw/irdma/verbs.c
> @@ -2028,13 +2028,24 @@ static void irdma_cq_free_rsrc(struct irdma_pci_f *rf, struct irdma_cq *iwcq)
>  		if (iwcq->iwpbl) {
>  			iwmr = iwcq->iwpbl->iwmr;
>  
> -			refcount_dec(&iwmr->user_ring_refs);
> +			if (iwmr && refcount_dec_and_test(&iwmr->user_ring_refs)) {
> +				ib_umem_release(iwmr->region);
> +				if (iwcq->iwpbl->pbl_allocated)
> +					irdma_free_pble(rf->pble_rsrc, &iwcq->iwpbl->pble_alloc);
> +				kfree(iwmr);
> +			}
>  		}

[Severity: High]
Does the introduction of 1-step CQs create a resource leak in 
irdma_resize_cq()?

When userspace resizes the CQ via ib_uverbs_resize_cq(), the kernel invokes 
irdma_resize_cq(). This function successfully swaps in the new PBL and drops 
the reference to the old MR:

drivers/infiniband/hw/irdma/verbs.c:irdma_resize_cq() {
...
	spin_lock_irqsave(&iwcq->lock, flags);
	if (udata) {
		struct irdma_pbl *old_iwpbl = iwcq->iwpbl;
		...
		iwcq->iwpbl = iwpbl_buf;
		if (old_iwpbl) {
			struct irdma_mr *old_iwmr = old_iwpbl->iwmr;

			refcount_dec(&old_iwmr->user_ring_refs);
		}
	}
...
}

For 1-step MRs, the refcount drops from 1 to 0 here. However, since 
irdma_resize_cq() doesn't use refcount_dec_and_test() with the explicit 
cleanup logic added to irdma_cq_free_rsrc(), it appears the MR struct, UMEM 
region, and PBLE resources will be permanently leaked.

If the cleanup logic is added to irdma_resize_cq(), it looks like it would 
cause a sleeping in atomic context bug if placed inside the spin_lock_irqsave 
region, since irdma_free_pble() acquires pble_mutex_lock. The cleanup would 
need to be deferred until after spin_unlock_irqrestore().

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261011011022.1445352-1-dhu@x6u.co?part=4

  reply	other threads:[~2026-10-11  1:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11  1:10 [PATCH rdma-next 0/5] RDMA/irdma: Add support for ioctl David Hu
2026-10-11  1:10 ` [PATCH rdma-next 1/5] RDMA/irdma: Plumb uverbs_attr_bundle for QP, SRQ David Hu
2026-10-11  1:18   ` sashiko-bot
2026-10-11  1:10 ` [PATCH rdma-next 2/5] RDMA/irdma: Register irdma UVERBS ioctl namespace David Hu
2026-10-11  1:20   ` sashiko-bot
2026-10-11  1:10 ` [PATCH rdma-next 3/5] RDMA/irdma: Support UMEM attribute for QP creation David Hu
2026-10-11  1:22   ` sashiko-bot
2026-10-11  1:10 ` [PATCH rdma-next 4/5] RDMA/irdma: Support UMEM attribute for CQ creation David Hu
2026-10-11  1:27   ` sashiko-bot [this message]
2026-10-12 14:17   ` Leon Romanovsky
2026-10-12 21:15     ` David Hu
2026-10-11  1:10 ` [PATCH rdma-next 5/5] RDMA/irdma: Support UMEM attribute for SRQ creation David Hu
2026-10-11  1:22   ` sashiko-bot

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-166959@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dhu@x6u.co \
    --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