All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
	Bob Pearson <rpearsonhpe@gmail.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next v2 0/9] ICRC cleanup
Date: Mon, 19 Jul 2021 14:10:00 -0300	[thread overview]
Message-ID: <20210719171000.GT543781@nvidia.com> (raw)
In-Reply-To: <CAN-5tyFrtf8SEet8at7QvwnFqLmdZoK2AaULXfXK-kq0_F8azw@mail.gmail.com>

On Mon, Jul 19, 2021 at 11:53:20AM -0400, Olga Kornievskaia wrote:
> On Mon, Jul 19, 2021 at 5:16 AM Zhu Yanjun <zyjzyj2000@gmail.com> wrote:
> >
> > On Sat, Jul 17, 2021 at 1:38 AM Jason Gunthorpe <jgg@nvidia.com> wrote:
> > >
> > > On Tue, Jul 06, 2021 at 11:00:32PM -0500, Bob Pearson wrote:
> > > > This series of patches is a cleanup of the ICRC code in the rxe driver.
> > > > The end result is to collect all the ICRC focused code into rxe_icrc.c
> > > > with three APIs that are used by the rest of the driver. One to initialize
> > > > the crypto engine used to compute crc32, and one each to generate and
> > > > check the ICRC in a packet.
> > > >
> > > > Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> > > > v2:
> > > >   Split up the 5 patches in the first version into 9 patches which are
> > > >   each focused on a single change.
> > > >   Fixed sparse warnings in the first version.
> > > >
> > > > Bob Pearson (9):
> > > >   RDMA/rxe: Move ICRC checking to a subroutine
> > > >   RDMA/rxe: Move rxe_xmit_packet to a subroutine
> > > >   RDMA/rxe: Fixup rxe_send and rxe_loopback
> > > >   RDMA/rxe: Move ICRC generation to a subroutine
> > > >   RDMA/rxe: Move rxe_crc32 to a subroutine
> > > >   RDMA/rxe: Fixup rxe_icrc_hdr
> > > >   RDMA/rxe: Move crc32 init code to rxe_icrc.c
> > > >   RDMA/rxe: Add kernel-doc comments to rxe_icrc.c
> > > >   RDMA/rxe: Fix types in rxe_icrc.c
> > >
> > > Applied to for-next, thanks
> >
> > Hi, Jason && Bob
> >
> > I confronted a problem.
> > One hosts with this patch series, A
> > other hosts, without this patch series, B
> >
> > I run rping between A <-------> B.
> >
> > I confronted the following errors, and rping can not succeed.
> > "
> > ...
> > [ 1848.251273] rdma_rxe: bad ICRC from 172.16.1.61
> > [ 1971.750691] rdma_rxe: bad ICRC from 172.16.1.61
> > ...
> > "
> > It seems that this patch series breaks the Backward compatibility of RXE.
> >
> > Not sure if it is a problem. Please comment.
> >
> > Thanks a lot.
> > Zhu Yanjun
> 
> I would like to second this post. I was about to submit a new post
> asking about why rxe isn't working and if it's known. I'm trying to
> figure out when/what patch broke things. From the stand point of
> NFSoRDMA, it stopped working and I have discovered that simple rping
> doesn't work as well. The last known working release was 5.11.

This isn't included in v5.13 or v5.14, so it can't be this series

You should send Bob and Zhu your non-working report

Jason

  reply	other threads:[~2021-07-19 17:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07  4:00 [PATCH for-next v2 0/9] ICRC cleanup Bob Pearson
2021-07-07  4:00 ` [PATCH v2 1/9] RDMA/rxe: Move ICRC checking to a subroutine Bob Pearson
2021-07-13  7:27   ` Zhu Yanjun
2021-07-16 15:55   ` Jason Gunthorpe
2021-07-07  4:00 ` [PATCH v2 2/9] RDMA/rxe: Move rxe_xmit_packet " Bob Pearson
2021-07-14  3:24   ` Zhu Yanjun
2021-07-07  4:00 ` [PATCH v2 3/9] RDMA/rxe: Fixup rxe_send and rxe_loopback Bob Pearson
2021-07-07  4:00 ` [PATCH v2 4/9] RDMA/rxe: Move ICRC generation to a subroutine Bob Pearson
2021-07-16 15:57   ` Jason Gunthorpe
2021-07-16 16:08     ` Bob Pearson
2021-07-16 16:29       ` Jason Gunthorpe
2021-07-16 16:38         ` Pearson, Robert B
2021-07-07  4:00 ` [PATCH v2 5/9] RDMA/rxe: Move rxe_crc32 " Bob Pearson
2021-07-07  4:00 ` [PATCH v2 6/9] RDMA/rxe: Fixup rxe_icrc_hdr Bob Pearson
2021-07-07  4:00 ` [PATCH v2 7/9] RDMA/rxe: Move crc32 init code to rxe_icrc.c Bob Pearson
2021-07-07  4:00 ` [PATCH v2 8/9] RDMA/rxe: Add kernel-doc comments " Bob Pearson
2021-07-07  4:00 ` [PATCH v2 9/9] RDMA/rxe: Fix types in rxe_icrc.c Bob Pearson
2021-07-16 16:06   ` Jason Gunthorpe
2021-07-08  7:36 ` [PATCH for-next v2 0/9] ICRC cleanup Zhu Yanjun
2021-07-16 17:38 ` Jason Gunthorpe
2021-07-19  8:42   ` Zhu Yanjun
2021-07-19 15:53     ` Olga Kornievskaia
2021-07-19 17:10       ` Jason Gunthorpe [this message]
2021-07-19 21:26         ` Bob Pearson

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=20210719171000.GT543781@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=aglo@umich.edu \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.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 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.