From: zhenwei pi <pizhenwei@bytedance.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>, jgg@ziepe.ca
Cc: zyjzyj2000@gmail.com, leon@kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] RDMA/rxe: Fix mismatched max_msg_sz
Date: Tue, 17 Dec 2024 11:37:45 +0800 [thread overview]
Message-ID: <9e833b88-4efe-48eb-a605-984f5ab7f49f@bytedance.com> (raw)
In-Reply-To: <affab92f-9a5b-481a-8816-8d5560721648@linux.dev>
On 12/17/24 00:47, Zhu Yanjun wrote:
> 在 2024/12/16 13:19, zhenwei pi 写道:
>> User mode queries max_msg_sz as 0x800000 by command 'ibv_devinfo -v',
>> however ibv_post_send/ibv_post_recv has a limit of 2^31. Fix this
>> mismatched information.
>>
>
> This is a buf fix. Perhaps Fixes tag is needed?
>
Hi,
Please amend this on applying patch:
Fixes: f605f26ea196 ("RDMA/rxe: Protect QP state with qp->state_lock")
Fixes: 5bf944f24129 ("RDMA/rxe: Add error messages")
If v2 is needed, please let me know.
>> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
>> ---
>> drivers/infiniband/sw/rxe/rxe_param.h | 2 +-
>> drivers/infiniband/sw/rxe/rxe_verbs.c | 5 ++---
>> 2 files changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/infiniband/sw/rxe/rxe_param.h b/drivers/
>> infiniband/sw/rxe/rxe_param.h
>> index d2f57ead78ad..003f681e5dc0 100644
>> --- a/drivers/infiniband/sw/rxe/rxe_param.h
>> +++ b/drivers/infiniband/sw/rxe/rxe_param.h
>> @@ -129,7 +129,7 @@ enum rxe_device_param {
>> enum rxe_port_param {
>> RXE_PORT_GID_TBL_LEN = 1024,
>> RXE_PORT_PORT_CAP_FLAGS = IB_PORT_CM_SUP,
>> - RXE_PORT_MAX_MSG_SZ = 0x800000,
>> + RXE_PORT_MAX_MSG_SZ = (1UL << 31),
>
> In the above, perhaps the parentheses is not necessary.
> Except that, I am fine with this.
>
> Thanks a lot.
> Review-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>
> Zhu Yanjun
>
>> RXE_PORT_BAD_PKEY_CNTR = 0,
>> RXE_PORT_QKEY_VIOL_CNTR = 0,
>> RXE_PORT_LID = 0,
>> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c b/drivers/
>> infiniband/sw/rxe/rxe_verbs.c
>> index 5c18f7e342f2..ffd5b07ad3e6 100644
>> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
>> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
>> @@ -688,7 +688,7 @@ static int validate_send_wr(struct rxe_qp *qp,
>> const struct ib_send_wr *ibwr,
>> for (i = 0; i < ibwr->num_sge; i++)
>> length += ibwr->sg_list[i].length;
>> - if (length > (1UL << 31)) {
>> + if (length > RXE_PORT_MAX_MSG_SZ) {
>> rxe_err_qp(qp, "message length too long\n");
>> break;
>> }
>> @@ -972,8 +972,7 @@ static int post_one_recv(struct rxe_rq *rq, const
>> struct ib_recv_wr *ibwr)
>> for (i = 0; i < num_sge; i++)
>> length += ibwr->sg_list[i].length;
>> - /* IBA max message size is 2^31 */
>> - if (length >= (1UL<<31)) {
>> + if (length > RXE_PORT_MAX_MSG_SZ) {
>> err = -EINVAL;
>> rxe_dbg("message length too long\n");
>> goto err_out;
>
next prev parent reply other threads:[~2024-12-17 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 12:19 [PATCH] RDMA/rxe: Fix mismatched max_msg_sz zhenwei pi
2024-12-16 16:47 ` Zhu Yanjun
2024-12-17 3:37 ` zhenwei pi [this message]
2024-12-17 14:37 ` Leon Romanovsky
2024-12-17 14:37 ` 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=9e833b88-4efe-48eb-a605-984f5ab7f49f@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
--cc=zyjzyj2000@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