From: Bernard Metzler <bernard.metzler@linux.dev>
To: Guoqing Jiang <guoqing.jiang@linux.dev>, jgg@ziepe.ca, leon@kernel.org
Cc: linux-rdma@vger.kernel.org, shuangpeng.kernel@gmail.com
Subject: Re: [PATCH] RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept
Date: Tue, 25 Aug 2026 15:53:33 +0200 [thread overview]
Message-ID: <de7ccaed-e270-459b-a34a-d32b2b2ce4e8@linux.dev> (raw)
In-Reply-To: <20260825130954.27327-1-guoqing.jiang@linux.dev>
On 25.08.2026 15:09, Guoqing Jiang wrote:
> We need to clear qp and cep before release state_lock as siw_qp_llp_closeo
> and siw_qp_modify->siw_qp_llp_close did.
>
> Otherwise if siw_qp_modify() fails in siw_accept(), the QP's state_lock
> is released before the error path cleanup. A concurrent ibv_modify_qp()
> transitioning the QP to ERROR can race in this window:
>
> siw_accept() ibv_modify_qp(ERROR)
> ---------------------- ----------------------
> siw_qp_modify() fails
> up_write(&qp->state_lock)
> down_write(&qp->state_lock)
> nextstate_from_idle():
> if (qp->cep)
> siw_cep_put(qp->cep) <- frees cep
> qp->cep = NULL
> goto error
> cep->qp = NULL <- UAF
>
> Clear qp->cep and cep->qp, and drop the association reference taken by
> siw_cep_get(), all under the write lock held from the initial
> down_write(&qp->state_lock). Thread B therefore sees qp->cep == NULL,
> skips its own put, and cannot free the cep before siw_accept() is done
> with it.
>
> Reported-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
> Link: https://lore.kernel.org/linux-rdma/d6fbe475-a5c2-f975-99b0-a0bd6b6d10e8@linux.dev/T/#m5876c1ff2de8686a9a1173b8f1aa0ff5363a785c
> Signed-off-by: Guoqing Jiang <guoqing.jiang@linux.dev>
> ---
> drivers/infiniband/sw/siw/siw_cm.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/sw/siw/siw_cm.c b/drivers/infiniband/sw/siw/siw_cm.c
> index 0245b25e7271..1573f2e888b2 100644
> --- a/drivers/infiniband/sw/siw/siw_cm.c
> +++ b/drivers/infiniband/sw/siw/siw_cm.c
> @@ -1719,9 +1719,13 @@ int siw_accept(struct iw_cm_id *id, struct iw_cm_conn_param *params)
> SIW_QP_ATTR_STATE | SIW_QP_ATTR_LLP_HANDLE |
> SIW_QP_ATTR_ORD | SIW_QP_ATTR_IRD |
> SIW_QP_ATTR_MPA);
> + if (rv) {
> + cep->qp = NULL;
This can better be omitted since done in error_unlock path
anyway and is redundant otherwise. It would also better
retain the logic of calling siw_qp_put(qp) right after
clearing cep's reference to the qp, as done in error path.
Thank you!
Bernard.> + qp->cep = NULL;
> + siw_cep_put(cep);
> + goto error_unlock;
> + }
> up_write(&qp->state_lock);
> - if (rv)
> - goto error;
>
> siw_dbg_cep(cep, "[QP %u]: send mpa reply, %d byte pdata\n",
> qp_id(qp), params->private_data_len);
next prev parent reply other threads:[~2026-08-25 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 13:09 [PATCH] RDMA/siw: Clear association under lock if siw_qp_modify fails in siw_accept Guoqing Jiang
2026-08-25 13:53 ` Bernard Metzler [this message]
2026-08-26 6:38 ` Guoqing Jiang
2026-08-26 12:19 ` Bernard Metzler
2026-08-26 13:15 ` Guoqing Jiang
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=de7ccaed-e270-459b-a34a-d32b2b2ce4e8@linux.dev \
--to=bernard.metzler@linux.dev \
--cc=guoqing.jiang@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=shuangpeng.kernel@gmail.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