From: Leon Romanovsky <leon@kernel.org>
To: Greg Sword <gregsword0@gmail.com>
Cc: Daisuke Matsuda <dskmtsd@gmail.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
jgg@ziepe.ca, zyjzyj2000@gmail.com, hch@infradead.org
Subject: Re: [PATCH for-next v3] RDMA/core: Avoid hmm_dma_map_alloc() for virtual DMA devices
Date: Tue, 27 May 2025 09:35:32 +0300 [thread overview]
Message-ID: <20250527063532.GZ7435@unreal> (raw)
In-Reply-To: <CAEz=Lcu3KtR5vNK5KbUcUzziit7z=rJofNQjVB-FA=35jiAseQ@mail.gmail.com>
On Tue, May 27, 2025 at 01:52:58AM +0800, Greg Sword wrote:
> On Sun, May 25, 2025 at 2:05 PM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > On Sun, May 25, 2025 at 05:27:23AM +0800, Greg Sword wrote:
> > > On Sat, May 24, 2025 at 10:43 PM Daisuke Matsuda <dskmtsd@gmail.com> wrote:
> > > >
> > > > Drivers such as rxe, which use virtual DMA, must not call into the DMA
> > > > mapping core since they lack physical DMA capabilities. Otherwise, a NULL
> > > > pointer dereference is observed as shown below. This patch ensures the RDMA
> > > > core handles virtual and physical DMA paths appropriately.
> >
> > <...>
> >
> > > > +EXPORT_SYMBOL(ib_dma_virt_map_alloc);
> > > > #endif /* CONFIG_INFINIBAND_VIRT_DMA */
> > > >
> > >
> > > Your ODP patches have caused significant issues, including system
> > > instability. The latest version of your patches has led to critical
> > > failures in our environment. Due to these ongoing problems, we have
> > > decided that our system will no longer incorporate your patches going
> > > forward.
> >
> > Please be civil and appreciate the work done by other people. Daisuke
> > invested a lot of effort to implement ODP which is very non-trivial part
> > of RDMA HW.
> >
> > If you can do it better, just do it, we will be happy to merge your
> > patches too.
> >
> > At the end, we are talking about -next branch, which has potential to be
> > unstable, so next time provide detailed bug report to support your claims.
> >
> > In addition, it was me who broke RXE.
>
> Is it an Honor?
It is a fact.
>
> >
> > Thanks
next prev parent reply other threads:[~2025-05-27 6:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 14:43 [PATCH for-next v3] RDMA/core: Avoid hmm_dma_map_alloc() for virtual DMA devices Daisuke Matsuda
2025-05-24 21:27 ` Greg Sword
2025-05-25 2:54 ` Daisuke Matsuda
2025-05-26 17:51 ` Greg Sword
2025-05-25 6:05 ` Leon Romanovsky
2025-05-26 17:52 ` Greg Sword
2025-05-27 6:35 ` Leon Romanovsky [this message]
2025-05-25 5:22 ` Zhu Yanjun
2025-05-25 6:03 ` Daisuke Matsuda
2025-05-25 14:17 ` Zhu Yanjun
2025-05-25 7:08 ` Leon Romanovsky
2025-05-25 9:34 ` Daisuke Matsuda
2025-05-25 10:24 ` Leon Romanovsky
2025-05-25 7:51 ` Leon Romanovsky
2025-05-26 6:57 ` Christoph Hellwig
2025-05-26 9:07 ` Leon Romanovsky
2025-05-26 19:57 ` 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=20250527063532.GZ7435@unreal \
--to=leon@kernel.org \
--cc=dskmtsd@gmail.com \
--cc=gregsword0@gmail.com \
--cc=hch@infradead.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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