From: Olga Kornievskaia <aglo@umich.edu>
To: Leon Romanovsky <leon@kernel.org>
Cc: Bob Pearson <rpearsonhpe@gmail.com>,
Zhu Yanjun <zyjzyj2000@gmail.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: RDMA/rxe is broken (impacting running NFSoRDMA over softRoCE)
Date: Wed, 21 Jul 2021 17:15:20 -0400 [thread overview]
Message-ID: <CAN-5tyEDF+KvSLxBNR_1vPdiJTDJMt1hc_ztk3E-J109x+Z4SA@mail.gmail.com> (raw)
In-Reply-To: <YPe02wEIHJffalro@unreal>
On Wed, Jul 21, 2021 at 1:47 AM Leon Romanovsky <leon@kernel.org> wrote:
>
> On Tue, Jul 20, 2021 at 05:48:03PM -0400, Olga Kornievskaia wrote:
> > On Tue, Jul 20, 2021 at 2:27 AM Bob Pearson <rpearsonhpe@gmail.com> wrote:
>
> <...>
>
> > There were a number of commits that lead to crashes. commit
> > ec9bf373f2458f4b5f1ece8b93a07e6204081667 "RDMA/core: Use refcount_t
> > instead of atomic_t on refcount of ib_uverbs_device" leads to the
> > following kernel oops. commit 205be5dc9984b67a3b388cbdaa27a2f2644a4bd6
> > "RDMA/irdma: Fix spelling mistake "Allocal" -> "Allocate"" also leads
> > to the kernel oops.
>
> The commits above aren't relevant to RXE at all.
>
> If first commit is wrong, all drivers will experience crashes and second
> commit is in irdma and not in RXE.
>
> And both of them are legit commits.
Yes I realize they are problems outside of rxe but I didn't run into
any crashes when I ran rpring on the 5.14-rc1 (it was hanging and
that's what I reported here) so I thought perhaps later patches have
addressed the crashes I've seen.
Would you like me to post a separate email report on the crash(es) (I
don't recall if it's the same one or two different ones)?
>
> Thanks
next prev parent reply other threads:[~2021-07-21 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 3:46 RDMA/rxe is broken (impacting running NFSoRDMA over softRoCE) Olga Kornievskaia
2021-07-20 6:27 ` Bob Pearson
2021-07-20 21:48 ` Olga Kornievskaia
2021-07-21 5:47 ` Leon Romanovsky
2021-07-21 21:15 ` Olga Kornievskaia [this message]
2021-07-21 21:48 ` Bob Pearson
2021-07-21 6:16 ` Zhu Yanjun
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=CAN-5tyEDF+KvSLxBNR_1vPdiJTDJMt1hc_ztk3E-J109x+Z4SA@mail.gmail.com \
--to=aglo@umich.edu \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--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 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).