lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEz=Lcu3KtR5vNK5KbUcUzziit7z=rJofNQjVB-FA=35jiAseQ@mail.gmail.com>
Date: Tue, 27 May 2025 01:52:58 +0800
From: Greg Sword <gregsword0@...il.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: Daisuke Matsuda <dskmtsd@...il.com>, linux-kernel@...r.kernel.org, 
	linux-rdma@...r.kernel.org, jgg@...pe.ca, zyjzyj2000@...il.com, 
	hch@...radead.org
Subject: Re: [PATCH for-next v3] RDMA/core: Avoid hmm_dma_map_alloc() for
 virtual DMA devices

On Sun, May 25, 2025 at 2:05 PM Leon Romanovsky <leon@...nel.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@...il.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?

>
> Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ