Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Selvin Xavier" <selvin.xavier@broadcom.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-rc 2/7] RDMA/bnxt_re: Honor a completion that races with a wait timeout
Date: Wed, 28 Oct 2026 06:20:08 +0000	[thread overview]
Message-ID: <sashiko-outbox-187556@kernel.org> (raw)
In-Reply-To: <20261028113404.33289-3-selvin.xavier@broadcom.com>

> If the wait helper gives up (timeout or firmware stall) and the CREQ
> tasklet processes the command before the waiter takes hwq->lock, the
> response is already copied into the caller's buffer and is_in_used is
> clear. The waiter still returns -ETIMEDOUT and may set
> FIRMWARE_STALL_DETECTED, and for CREATE_AH the handler skips
> destroy_timedout_ah() because the waiter was alive, so the AH leaks in
> firmware.
> 
> Under the lock, if the slot no longer holds this command's response
> buffer, a completion was delivered. Use its status instead of failing.
> 
> To keep that check valid, never reuse a cookie slot that is still in
> use: __send_message() returns -EAGAIN and __send_message_no_waiter()
> drops the internal command.
> 
> A slot stays in use only while its completion is outstanding. If that
> completion never arrives, the cause is a PCI error or firmware still
> processing the command, so there is no point in posting more commands.
> Continuing to return -EAGAIN until firmware completes the command in
> order is intended; otherwise recovery is initiated.
> 
> An internal destroy_ah dropped for the same reason leaks the AH in
> firmware; this is accepted and the comment in
> bnxt_qplib_service_creq() is updated to say so.
> 
> Fixes: 691eb7c6110f ("RDMA/bnxt_re: handle command completions after driver detect a timedout")
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261028113404.33289-1-selvin.xavier@broadcom.com?part=2


  reply	other threads:[~2026-10-28  6:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 11:33 [PATCH for-rc 0/7] RDMA/bnxt_re: Bug fixes for RCFW completion handling and verbs Selvin Xavier
2026-10-28 11:33 ` [PATCH for-rc 1/7] RDMA/bnxt_re: Clear stale RCFW resp pointer when wait ends Selvin Xavier
2026-10-28  6:18   ` sashiko-bot
2026-10-28 11:33 ` [PATCH for-rc 2/7] RDMA/bnxt_re: Honor a completion that races with a wait timeout Selvin Xavier
2026-10-28  6:20   ` sashiko-bot [this message]
2026-10-28 11:34 ` [PATCH for-rc 3/7] RDMA/bnxt_re: Do not treat CQ error notification as a command completion Selvin Xavier
2026-10-28  6:19   ` sashiko-bot
2026-10-28 11:34 ` [PATCH for-rc 4/7] RDMA/bnxt_re: Drop RCFW completions for cookies with no outstanding command Selvin Xavier
2026-10-28  6:17   ` sashiko-bot
2026-10-28 11:34 ` [PATCH for-rc 5/7] RDMA/bnxt_re: Reset cqe pointer each poll_cq iteration Selvin Xavier
2026-10-28  6:25   ` sashiko-bot
2026-10-28 11:34 ` [PATCH for-rc 6/7] RDMA/bnxt_re: Remove shared page mmap entry on alloc_ucontext failure Selvin Xavier
2026-10-28  6:17   ` sashiko-bot
2026-10-28 11:34 ` [PATCH for-rc 7/7] RDMA/bnxt_re: Bound FRMR page list by max_num_sg Selvin Xavier
2026-10-28  6:18   ` 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-187556@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=selvin.xavier@broadcom.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