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: <YThXe4WxHErNiwgE@infradead.org>
Date:   Wed, 8 Sep 2021 07:26:03 +0100
From:   Christoph Hellwig <hch@...radead.org>
To:     Shunsuke Mie <mie@...l.co.jp>
Cc:     Zhu Yanjun <zyjzyj2000@...il.com>,
        Christian K??nig <christian.koenig@....com>,
        Alex Deucher <alexander.deucher@....com>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Doug Ledford <dledford@...hat.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Jianxin Xiong <jianxin.xiong@...el.com>,
        Leon Romanovsky <leon@...nel.org>,
        linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
        dhobsong@...l.co.jp, taki@...l.co.jp, etom@...l.co.jp
Subject: Re: [RFC PATCH 1/3] RDMA/umem: Change for rdma devices has not dma
 device

On Wed, Sep 08, 2021 at 03:16:09PM +0900, Shunsuke Mie wrote:
> To share memory space using dma-buf, a API of the dma-buf requires dma
> device, but devices such as rxe do not have a dma device. For those case,
> change to specify a device of struct ib instead of the dma device.

So if dma-buf doesn't actually need a device to dma map why do we ever
pass the dma_device here?  Something does not add up.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ