From: Leon Romanovsky <leonro@nvidia.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "Marciniszyn, Mike" <mike.marciniszyn@cornelisnetworks.com>,
"Jason Gunthorpe" <jgg@nvidia.com>,
Haakon Bugge <haakon.bugge@oracle.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"Dalessandro, Dennis" <dennis.dalessandro@cornelisnetworks.com>,
Doug Ledford <dledford@redhat.com>
Subject: Re: NFS RDMA test failure as of 5.14-rc1
Date: Wed, 28 Jul 2021 07:31:13 +0300 [thread overview]
Message-ID: <YQDdkZ83yYI4US3A@unreal> (raw)
In-Reply-To: <9D442FCF-D0F8-40F1-9AA1-B85BAE91631A@oracle.com>
On Tue, Jul 27, 2021 at 11:10:25PM +0000, Chuck Lever III wrote:
>
> > On Jul 27, 2021, at 5:20 PM, Marciniszyn, Mike <mike.marciniszyn@cornelisnetworks.com> wrote:
> >
> >>> Haakon's original analysis said that this was an INIT->INIT
> >>> transition, so I'm a bit confused why we lost a RESET->INIT transition
> >>> in the end?
> >>
> >> Perhaps the patch should have removed the ib_modify_qp() from
> >> cma_modify_qp_rtr() instead.
> >
> > I think that will work.
>
> Implemented and tested. It doesn't work. :-)
>
> The conclusion I draw is that there are still spots that depend
> on one or the other of those state transitions remaining where
> they are.
So let's revert this patch.
Thanks
>
> --
> Chuck Lever
>
>
>
next prev parent reply other threads:[~2021-07-28 4:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 13:43 NFS RDMA test failure as of 5.14-rc1 Marciniszyn, Mike
2021-07-27 17:14 ` Marciniszyn, Mike
2021-07-27 17:26 ` Chuck Lever III
2021-07-27 17:35 ` Marciniszyn, Mike
2021-07-27 17:38 ` Jason Gunthorpe
2021-07-27 17:45 ` Chuck Lever III
2021-07-27 21:20 ` Marciniszyn, Mike
2021-07-27 23:10 ` Chuck Lever III
2021-07-28 4:31 ` Leon Romanovsky [this message]
2021-07-27 18:12 ` Leon Romanovsky
2021-07-27 20:17 ` Marciniszyn, Mike
2021-07-28 13:50 ` Marciniszyn, Mike
2021-07-28 17:05 ` Jason Gunthorpe
2021-07-29 18:28 ` Marciniszyn, Mike
2021-08-09 13:38 ` Haakon Bugge
2021-08-09 14:00 ` Chuck Lever III
2021-08-10 15:09 ` Marciniszyn, Mike
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=YQDdkZ83yYI4US3A@unreal \
--to=leonro@nvidia.com \
--cc=chuck.lever@oracle.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=haakon.bugge@oracle.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@cornelisnetworks.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.