From: Zhu Yanjun <zyjzyj2000@gmail.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Bob Pearson <rpearson@hpe.com>, Frank Zago <frank.zago@hpe.com>
Subject: Re: [PATCH for-next] RDMA/rxe: Fix a bug in rxe_fill_ip_info()
Date: Wed, 21 Apr 2021 13:38:44 +0800 [thread overview]
Message-ID: <CAD=hENcpo=gtYJOsgQ0jP=Vi6Dv0piFR8sCKCmksJ=PijXh1Cg@mail.gmail.com> (raw)
In-Reply-To: <20210421035952.4892-1-rpearson@hpe.com>
Thanks.
Acked-by: Zhu Yanjun <zyjzyj2000@gmail.com>
Zhu Yanjun
On Wed, Apr 21, 2021 at 12:01 PM Bob Pearson <rpearsonhpe@gmail.com> wrote:
>
> Fix a bug in rxe_fill_ip_info() which was attempting to convert from
> RDMA_NETWORK_XXX to RXE_NETWORK_XXX. .._IPV6 should have mapped to .._IPV6
> not .._IPV4.
>
> Fixes: edebc8407b88 ("RDMA/rxe: Fix small problem in network_type patch")
> Suggested-by: Frank Zago <frank.zago@hpe.com>
> Signed-off-by: Bob Pearson <rpearson@hpe.com>
> ---
> drivers/infiniband/sw/rxe/rxe_av.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_av.c b/drivers/infiniband/sw/rxe/rxe_av.c
> index df0d173d6acb..da2e867a1ed9 100644
> --- a/drivers/infiniband/sw/rxe/rxe_av.c
> +++ b/drivers/infiniband/sw/rxe/rxe_av.c
> @@ -88,7 +88,7 @@ void rxe_av_fill_ip_info(struct rxe_av *av, struct rdma_ah_attr *attr)
> type = RXE_NETWORK_TYPE_IPV4;
> break;
> case RDMA_NETWORK_IPV6:
> - type = RXE_NETWORK_TYPE_IPV4;
> + type = RXE_NETWORK_TYPE_IPV6;
> break;
> default:
> /* not reached - checked in rxe_av_chk_attr */
> --
> 2.27.0
>
next prev parent reply other threads:[~2021-04-21 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 3:59 [PATCH for-next] RDMA/rxe: Fix a bug in rxe_fill_ip_info() Bob Pearson
2021-04-21 5:38 ` Zhu Yanjun [this message]
2021-04-21 19:17 ` Jason Gunthorpe
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='CAD=hENcpo=gtYJOsgQ0jP=Vi6Dv0piFR8sCKCmksJ=PijXh1Cg@mail.gmail.com' \
--to=zyjzyj2000@gmail.com \
--cc=frank.zago@hpe.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.com \
--cc=rpearsonhpe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.