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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 14 May 2020 11:08:52 +0900
From:   David Stevens <>
To:     Daniel Vetter <>
Cc:     Tomasz Figa <>,
        Gerd Hoffmann <>,
        David Airlie <>,
        "Michael S . Tsirkin" <>,
        Jason Wang <>,
        Sumit Semwal <>,
        Maarten Lankhorst <>,
        Maxime Ripard <>,
        Thomas Zimmermann <>,
        Linux Kernel Mailing List <>,
        dri-devel <>,
        "open list:VIRTIO CORE, NET..." 
        "moderated list:DMA BUFFER SHARING FRAMEWORK" 
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 <> wrote:
> On Wed, Mar 11, 2020 at 12:20 PM David Stevens <> 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 <>
> 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:

> - 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

Powered by blists - more mailing lists