From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, leonro@nvidia.com, yangx.jy@fujitsu.com,
lizhijian@fujitsu.com, matsuda-daisuke@fujitsu.com,
tom@talpey.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v4] Subject: RDMA/rxe: Handle zero length rdma
Date: Thu, 16 Feb 2023 11:58:32 -0400 [thread overview]
Message-ID: <Y+5SqKC85AagX10A@nvidia.com> (raw)
In-Reply-To: <20230202044240.6304-1-rpearsonhpe@gmail.com>
On Wed, Feb 01, 2023 at 10:42:41PM -0600, Bob Pearson wrote:
> Currently the rxe driver does not handle all cases of zero length
> rdma operations correctly. The client does not have to provide an
> rkey for zero length RDMA read or write operations so the rkey
> provided may be invalid and should not be used to lookup an mr.
>
> This patch corrects the driver to ignore the provided rkey if the
> reth length is zero for read or write operations and make sure to
> set the mr to NULL. In read_reply() if length is zero rxe_recheck_mr()
> is not called. Warnings are added in the routines in rxe_mr.c to
> catch NULL MRs when the length is non-zero.
>
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> Reviewed-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
> ---
> v4:
> Fixed a regression in flush operations because the rkey must be
> valid in that case even if the length is zero which maybe the
> case for selectivity level of the entire memory region.
>
> Reported-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
Applied to for-next, I added a fixes line for day 0
Jason
prev parent reply other threads:[~2023-02-16 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 4:42 [PATCH for-next v4] Subject: RDMA/rxe: Handle zero length rdma Bob Pearson
2023-02-03 10:00 ` Daisuke Matsuda (Fujitsu)
2023-02-03 18:47 ` Bob Pearson
2023-02-08 7:12 ` Daisuke Matsuda (Fujitsu)
2023-02-08 8:41 ` lizhijian
2023-02-09 8:14 ` Daisuke Matsuda (Fujitsu)
2023-02-09 10:20 ` lizhijian
2023-02-13 9:32 ` Daisuke Matsuda (Fujitsu)
2023-02-13 17:41 ` Bob Pearson
2023-02-14 1:13 ` Zhu Yanjun
2023-02-16 15:58 ` Jason Gunthorpe [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=Y+5SqKC85AagX10A@nvidia.com \
--to=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=matsuda-daisuke@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=tom@talpey.com \
--cc=yangx.jy@fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).