The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Michael Gur <michaelgur@nvidia.com>
To: Honggang LI <honggangli@163.com>,
	jinpu.wang@ionos.com, danil.kipnis@cloud.ionos.com
Cc: jgg@ziepe.ca, leon@kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/rtrs: client: Fix clt_path::max_pages_per_mr calculation
Date: Tue, 23 Dec 2025 16:08:19 +0200	[thread overview]
Message-ID: <eb0d0439-c09b-4c10-be5d-a338ede83742@nvidia.com> (raw)
In-Reply-To: <20251223034324.13706-1-honggangli@163.com>


On 12/23/2025 5:43 AM, Honggang LI wrote:
> If the low two bytes of ib_dev::attrs::max_mr_size are zeros, the `min3`
> function will set clt_path::max_pages_per_mr to zero.

Can't see how if the low two bytes of max_mr_size are zero it would 
cause the local variable max_pages_per_mr to zero.
The more probable cause is that max_mr_size bits in the range 
[mr_page_shift+31:mr_page_shift] are zero. Since that's what's left 
after division and cast to u32.
This means you are working on a device supporting more pages_per_mr than 
can fit in a u32.

> `alloc_path_reqs` will pass zero, which is invalid,  as the third parameter
> to `ib_alloc_mr`.
>
> Fixes: 6a98d71daea1 ("RDMA/rtrs: client: main functionality")
> Signed-off-by: Honggang LI <honggangli@163.com>
> ---
>   drivers/infiniband/ulp/rtrs/rtrs-clt.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/ulp/rtrs/rtrs-clt.c b/drivers/infiniband/ulp/rtrs/rtrs-clt.c
> index 71387811b281..b9d66e4fab07 100644
> --- a/drivers/infiniband/ulp/rtrs/rtrs-clt.c
> +++ b/drivers/infiniband/ulp/rtrs/rtrs-clt.c
> @@ -1465,7 +1465,7 @@ static void query_fast_reg_mode(struct rtrs_clt_path *clt_path)
>   	max_pages_per_mr   = ib_dev->attrs.max_mr_size;
>   	do_div(max_pages_per_mr, (1ull << mr_page_shift));
>   	clt_path->max_pages_per_mr =
> -		min3(clt_path->max_pages_per_mr, (u32)max_pages_per_mr,
> +		min(min_not_zero(clt_path->max_pages_per_mr, (u32)max_pages_per_mr),

This still fixes the issue, but for readability, if max_pages_per_mr is 
larger than U32_MAX, I'd set it to be U32_MAX.

Michael

  reply	other threads:[~2025-12-23 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23  3:43 [PATCH] RDMA/rtrs: client: Fix clt_path::max_pages_per_mr calculation Honggang LI
2025-12-23 14:08 ` Michael Gur [this message]
2025-12-24  2:11   ` Honggang LI

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=eb0d0439-c09b-4c10-be5d-a338ede83742@nvidia.com \
    --to=michaelgur@nvidia.com \
    --cc=danil.kipnis@cloud.ionos.com \
    --cc=honggangli@163.com \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@ionos.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@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