From: sashiko-bot@kernel.org
To: "Nguyễn Văn Cao Nguyên" <nguyennvc@greennode.ai>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-rc] RDMA/irdma: Do not move a fresh RoCE QP to ERROR on RESET
Date: Wed, 30 Sep 2026 08:02:05 +0000 [thread overview]
Message-ID: <20260930080205.B331E1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930-irdma-reset-fresh-qp-v1-1-065327274e2b@greennode.ai>
> From: Nguyễn Văn Cao Nguyên <nguyennvc@greennode.ai>
>
> irdma_modify_qp_roce() handles IB_QPS_RESET like IB_QPS_ERR and moves
> the QP to ERROR. On a QP that was never moved to INIT, this makes the
> following RESET->INIT fail with -EINVAL, while ibv_query_qp() still
> reports RESET.
>
> RESET->RESET is a valid transition. The Mooncake transfer engine
> resets every new QP before INIT, so it cannot connect over an E810,
> while mlx5 accepts the same sequence:
>
> ibv_create_qp(RC) -> RESET
> ibv_modify_qp(RESET) -> 0
> ibv_modify_qp(INIT, ...) -> -EINVAL
>
> Skip the hardware modify when the QP has not been moved to INIT yet
> (iwarp_state is IRDMA_QP_STATE_INVALID), as there is nothing to flush.
> RESET after INIT still goes to ERROR.
>
> Fixes: b48c24c2d710 ("RDMA/irdma: Implement device supported verb APIs")
> Assisted-by: LLM
> Signed-off-by: Nguyễn Văn Cao Nguyên <nguyennvc@greennode.ai>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930-irdma-reset-fresh-qp-v1-1-065327274e2b@greennode.ai?part=1
next prev parent reply other threads:[~2026-09-30 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 7:51 [PATCH rdma-rc] RDMA/irdma: Do not move a fresh RoCE QP to ERROR on RESET Nguyễn Văn Cao Nguyên via B4 Relay
2026-09-30 7:51 ` Nguyễn Văn Cao Nguyên
2026-09-30 8:02 ` sashiko-bot [this message]
2026-09-30 13:48 ` Leon Romanovsky
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=20260930080205.B331E1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nguyennvc@greennode.ai \
--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 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.