mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kensanya  <kensanya@163.com>
To: "Leon Romanovsky" <leon@kernel.org>
Cc: bvanassche@acm.org, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	target-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	TanZheng <tanzheng@kylinos.cn>
Subject: Re:Re:Re: [PATCH] RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters
Date: Wed, 15 Jul 2026 18:08:59 +0800 (CST)	[thread overview]
Message-ID: <13fef285.8313.19f6540496d.Coremail.kensanya@163.com> (raw)
In-Reply-To: <6c3eb2da.8145.19f653637b1.Coremail.kensanya@163.com>


















At 2026-07-15 17:57:59, "kensanya" <kensanya@163.com> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>At 2026-07-15 17:05:57, "Leon Romanovsky" <leon@kernel.org> wrote:
>>On Wed, Jul 15, 2026 at 10:30:16AM +0800, kensanya@163.com wrote:
>>> From: TanZheng <tanzheng@kylinos.cn>
>>> 
>>> When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect
>>> descriptor, the unwind path destroys RDMA contexts but leaves stale
>>> n_rw_ctx and n_rdma values (and a dangling rw_ctxs pointer). Later
>>> sq_wr_avail accounting in srpt_queue_response() or srpt_write_pending()
>>> can then subtract the wrong number of send queue credits.
>>> 
>>> Reset the counters and rw_ctxs pointer before returning an error.
>>> 
>>> Fixes: b99f8e4d7bcd ("IB/srpt: convert to the generic RDMA READ/WRITE API")
>>> Signed-off-by: TanZheng <tanzheng@kylinos.cn>
>>> ---
>>>  drivers/infiniband/ulp/srpt/ib_srpt.c | 3 +++
>>>  1 file changed, 3 insertions(+)
>>> 
>>> diff --git a/drivers/infiniband/ulp/srpt/ib_srpt.c b/drivers/infiniband/ulp/srpt/ib_srpt.c
>>> index f66cfd70c263..4644429fae14 100644
>>> --- a/drivers/infiniband/ulp/srpt/ib_srpt.c
>>> +++ b/drivers/infiniband/ulp/srpt/ib_srpt.c
>>> @@ -1016,6 +1016,9 @@ static int srpt_alloc_rw_ctxs(struct srpt_send_ioctx *ioctx,
>>>  	}
>>>  	if (ioctx->rw_ctxs != &ioctx->s_rw_ctx)
>>>  		kfree(ioctx->rw_ctxs);
>>> +	ioctx->rw_ctxs = &ioctx->s_rw_ctx;
>>
>>This line seems questionable to me.
>>You probably need to write:
>>if (ioctx->rw_ctxs != &ioctx->s_rw_ctx) {
>>  kfree(ioctx->rw_ctxs);
>>  ioctx->rw_ctxs = NULL;
>>}
>>
>>> +	ioctx->n_rw_ctx = 0;
>>> +	ioctx->n_rdma = 0;
>>
>>These lines seem correct to me.
>>
>>>  	return ret;
>>>  }
>>>  
>>> -- 
>>> 2.25.1
>>> 
>Hi Bart,
>
>Thanks for the review.
>
>I originally set rw_ctxs back to &ioctx->s_rw_ctx after kfree()
>because that is the only other valid value used in this file
>(nbufs == 1 path), and I wanted to clear the dangling pointer
>while keeping the existing "embedded vs heap" convention.
>
>This is indeed misleading.I will change it to:
>	if (ioctx->rw_ctxs != &ioctx->s_rw_ctx) {
>		kfree(ioctx->rw_ctxs);
>		ioctx->rw_ctxs = NULL;
>	}
>and keep the n_rw_ctx / n_rdma resets. Will send a v2.
>
>Thanks,
>TanZheng
>
Hi Leon.

I'm very sorry, I made a mistake.

Thanks,
TanZheng

      reply	other threads:[~2026-07-15 10:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15  2:30 kensanya
2026-07-15  9:05 ` Leon Romanovsky
2026-07-15  9:57   ` kensanya
2026-07-15 10:08     ` kensanya [this message]

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=13fef285.8313.19f6540496d.Coremail.kensanya@163.com \
    --to=kensanya@163.com \
    --cc=bvanassche@acm.org \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tanzheng@kylinos.cn \
    --cc=target-devel@vger.kernel.org \
    /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

Powered by JetHome