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
| ||
|
Date: Thu, 14 May 2020 09:59:52 +0200 From: Gerd Hoffmann <kraxel@...hat.com> To: Daniel Vetter <daniel@...ll.ch> Cc: David Stevens <stevensd@...omium.org>, Tomasz Figa <tfiga@...omium.org>, 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 Hi, > - 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, Gerd
Powered by blists - more mailing lists