Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jaeyeong Lee" <lee@jaeyeong.cc>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/irdma: publish APBVT entries after hardware setup
Date: Wed, 11 Nov 2026 09:36:07 +0000	[thread overview]
Message-ID: <sashiko-outbox-208705@kernel.org> (raw)
In-Reply-To: <20261111092505.3121847-1-lee@jaeyeong.cc>

> irdma_add_apbvt() inserts a new entry into apbvt_hash_tbl before
> sending the CQP command that creates the hardware entry. If the command
> fails, the entry is freed without being removed from the hash table. A
> later lookup of the same port traverses the freed entry.
> 
> Removing the entry on failure is not sufficient because another thread
> can find it and increment use_cnt while the CQP command is in progress.
> 
> Serialize APBVT additions and publish new entries only after the hardware
> command succeeds. Since the allocation no longer runs under apbvt_lock,
> use GFP_KERNEL.
> 
> The issue was found by static analysis and confirmed with a KASAN
> reproducer that forces the CQP failure and retries the same port.
> 
> [ ... ]
>  init_module+0x210/0xff0 [irdma_apbvt_repro]
> 
> Fixes: 44d9e52977a1 ("RDMA/irdma: Implement device initialization definitions")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jaeyeong Lee <lee@jaeyeong.cc>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111092505.3121847-1-lee@jaeyeong.cc?part=1


  reply	other threads:[~2026-11-11  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  9:25 [PATCH] RDMA/irdma: publish APBVT entries after hardware setup Jaeyeong Lee
2026-11-11  9:36 ` sashiko-bot [this message]
2026-11-11 15:15 ` Jacob Moroni

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-208705@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=lee@jaeyeong.cc \
    --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