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]
Date:   Fri, 13 Jan 2017 21:59:32 +0000
From:   Bart Van Assche <Bart.VanAssche@...disk.com>
To:     "alex.estrin@...el.com" <alex.estrin@...el.com>,
        "dledford@...hat.com" <dledford@...hat.com>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 00/26] IB: Optimize DMA mapping

On Fri, 2017-01-13 at 21:08 +0000, Estrin, Alex wrote:
> It didn't fix the failure... Apparently there is an issue with generic
> mapping itself. 

Hello Alex,

The generic mapping code in lib/dma-virt.c works fine with at least the rxe
driver. Additionally, as far as I can see the mapping code in lib/dma-virt.c
is identical to the mapping in drivers/infiniband/sw/rdmavt/dma.c. What is
not clear to me however is how my patches can have caused the SDMA engine
error messages? As far as I can see the code in
drivers/infiniband/hw/hfi1/sdma.c uses PCI DMA mapping operations instead of
the generic dma_virt_ops. Is that correct?

Thanks,

Bart.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ