From: Jason Gunthorpe <jgg@nvidia.com>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"trondmy@kernel.org" <trondmy@kernel.org>
Subject: Re: [PATCH] RDMA: null pointer in __ib_umem_release causes kernel panic
Date: Wed, 5 Jan 2022 13:43:55 -0400 [thread overview]
Message-ID: <20220105174355.GU2328285@nvidia.com> (raw)
In-Reply-To: <f6480329a7d86e5eb10f11b5bc5049868981dd3d.camel@hammerspace.com>
On Wed, Jan 05, 2022 at 05:16:06PM +0000, Trond Myklebust wrote:
> > I'm confused, RPC/RDMA should never touch a umem at all.
> >
> > Is this really the other bug where user and kernel MR are getting
> > confused?
> >
>
> As far as I know, RPC/RDMA is just using the RDMA api to register and
> unregister chunks of memory, so it is definitely not directly touching
> the umem.
I mean, RPC/RDMA doesn't have a umem at all, so seeing it any stack
trace says something is corrupted
I suppose it is this:
https://lore.kernel.org/r/20211222101312.1358616-1-maorg@nvidia.com
Jason
next prev parent reply other threads:[~2022-01-05 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 14:18 [PATCH] RDMA: null pointer in __ib_umem_release causes kernel panic trondmy
2022-01-05 14:37 ` Jason Gunthorpe
2022-01-05 15:02 ` Trond Myklebust
2022-01-05 16:09 ` Jason Gunthorpe
2022-01-05 17:16 ` Trond Myklebust
2022-01-05 17:43 ` Jason Gunthorpe [this message]
2022-01-05 17:49 ` Trond Myklebust
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=20220105174355.GU2328285@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--cc=trondmy@kernel.org \
/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).