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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 14 May 2020 09:59:52 +0200
From:   Gerd Hoffmann <>
To:     Daniel Vetter <>
Cc:     David Stevens <>,
        Tomasz Figa <>,
        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


> - for the runtime upcasting the usual approach is to check the ->ops
> pointer. Which means that would need to be the same for all virtio
> dma_bufs, which might get a bit awkward. But I'd really prefer we not
> add allocator specific stuff like this to dma-buf.

This is exactly the problem, it gets messy quickly, also when it comes
to using the drm_prime.c helpers ...

take care,

Powered by blists - more mailing lists