diff options
| author | Thomas Zimmermann <[email protected]> | 2025-07-15 15:58:13 +0000 |
|---|---|---|
| committer | Thomas Zimmermann <[email protected]> | 2025-07-17 10:26:19 +0000 |
| commit | bb7f4972a6ff9a537b87e1b0ecf0e561f2761dd3 (patch) | |
| tree | 0f70c5003e23098cdf2a475c6601998392c18aa7 /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | |
| parent | Revert "drm/vmwgfx: Use dma_buf from GEM object instance" (diff) | |
| download | kernel-bb7f4972a6ff9a537b87e1b0ecf0e561f2761dd3.tar.gz kernel-bb7f4972a6ff9a537b87e1b0ecf0e561f2761dd3.zip | |
Revert "drm/etnaviv: Use dma_buf from GEM object instance"
This reverts commit e91eb3ae415472b28211d7fed07fa283845b311e.
The dma_buf field in struct drm_gem_object is not stable over the
object instance's lifetime. The field becomes NULL when user space
releases the final GEM handle on the buffer object. This resulted
in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on
GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem
partially. They especially don't work for buffer objects without a DRM
framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
Signed-off-by: Thomas Zimmermann <[email protected]>
Reviewed-by: Simona Vetter <[email protected]>
Acked-by: Christian König <[email protected]>
Acked-by: Zack Rusin <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_device.c')
0 files changed, 0 insertions, 0 deletions