linux-kernel - Re: [PATCH v2] staging: android: ion: Add implementation of dma_buf_vmap and dma_buf

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:   Tue, 30 Jan 2018 23:15:01 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Alexey Skidanov <alexey.skidanov@...el.com>
Cc:     devel@...verdev.osuosl.org, labbott@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] staging: android: ion: Add implementation of
 dma_buf_vmap and dma_buf_vunmap

On Tue, Jan 30, 2018 at 10:39:13PM +0200, Alexey Skidanov wrote:
> dma_buf_vmap and dma_buf_vunmap allow drivers to access buffers, created by ion.

But why would anyone ever want to do that?  What is wrong with the
existing interfaces that drivers use to access buffers created by ion?

What code uses this new interface?

We need a bit more information please.

thanks,

greg k-h