diff options
| author | Laurent Pinchart <laurent.pinchart@ideasonboard.com> | 2017-05-08 21:59:24 +0300 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2017-06-02 10:57:08 +0300 |
| commit | c488dd2048662f35c56d002379221edf1a2a9404 (patch) | |
| tree | 30ba3a66adb5ce303f922700bc0ef01122d7a982 /drivers/gpu/drm/imx/Kconfig | |
| parent | 97817fd46518aa2f457ce41f6a9aecd36b461426 (diff) | |
| download | linux-c488dd2048662f35c56d002379221edf1a2a9404.tar.xz | |
drm: omapdrm: Take GEM object reference when exporting dmabuf
To ensure that neither the GEM object nor the DRM device goes away while
a GEM object exported through dma-buf is still accessible, references
must be taken to both the GEM object and the DRM device at export time.
The dma-buf release handler already releases the GEM object, but the
export handler doesn't take a corresponding reference, which results in
a refcount underflow.
Fix this by replacing the custom implementation by
drm_gem_dmabuf_export() and drm_gem_dmabuf_release() that handle
reference counting for us.
Fixes: 6ad11bc3a0b8 ("staging: drm/omap: dmabuf/prime support")
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Diffstat (limited to 'drivers/gpu/drm/imx/Kconfig')
0 files changed, 0 insertions, 0 deletions