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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 14 May 2020 11:08:52 +0900 From: David Stevens <stevensd@...omium.org> To: Daniel Vetter <daniel@...ll.ch> Cc: Tomasz Figa <tfiga@...omium.org>, Gerd Hoffmann <kraxel@...hat.com>, David Airlie <airlied@...ux.ie>, "Michael S . Tsirkin" <mst@...hat.com>, Jason Wang <jasowang@...hat.com>, Sumit Semwal <sumit.semwal@...aro.org>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, dri-devel <dri-devel@...ts.freedesktop.org>, "open list:VIRTIO CORE, NET..." <virtualization@...ts.linux-foundation.org>, "open list:DMA BUFFER SHARING FRAMEWORK" <linux-media@...r.kernel.org>, "moderated list:DMA BUFFER SHARING FRAMEWORK" <linaro-mm-sig@...ts.linaro.org>, virtio-dev@...ts.oasis-open.org Subject: Re: [PATCH v3 1/4] dma-buf: add support for virtio exported objects On Thu, May 14, 2020 at 12:45 AM Daniel Vetter <daniel@...ll.ch> wrote: > On Wed, Mar 11, 2020 at 12:20 PM David Stevens <stevensd@...omium.org> wrote: > > > > This change adds a new dma-buf operation that allows dma-bufs to be used > > by virtio drivers to share exported objects. The new operation allows > > the importing driver to query the exporting driver for the UUID which > > identifies the underlying exported object. > > > > Signed-off-by: David Stevens <stevensd@...omium.org> > > Adding Tomasz Figa, I've discussed this with him at elce last year I > think. Just to make sure. > > Bunch of things: > - obviously we need the users of this in a few drivers, can't really > review anything stand-alone Here is a link to the usage of this feature by the currently under development virtio-video driver: https://markmail.org/thread/j4xlqaaim266qpks > - adding very specific ops to the generic interface is rather awkward, > eventually everyone wants that and we end up in a mess. I think the > best solution here would be if we create a struct virtio_dma_buf which > subclasses dma-buf, add a (hopefully safe) runtime upcasting > functions, and then a virtio_dma_buf_get_uuid() function. Just storing > the uuid should be doable (assuming this doesn't change during the > lifetime of the buffer), so no need for a callback. So you would prefer a solution similar to the original version of this patchset? https://markmail.org/message/z7if4u56q5fmaok4
Powered by blists - more mailing lists