aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
diff options
context:
space:
mode:
authorThomas Zimmermann <[email protected]>2025-07-15 15:58:12 +0000
committerThomas Zimmermann <[email protected]>2025-07-17 10:26:19 +0000
commit1e9d2aed7c2248bc5ba7d0dfea4fcc0b2f80b4f7 (patch)
treefb2cabe5319d18514e0aa47f3bae97f544f25dcf /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
parentRevert "drm/virtio: Use dma_buf from GEM object instance" (diff)
downloadkernel-1e9d2aed7c2248bc5ba7d0dfea4fcc0b2f80b4f7.tar.gz
kernel-1e9d2aed7c2248bc5ba7d0dfea4fcc0b2f80b4f7.zip
Revert "drm/vmwgfx: Use dma_buf from GEM object instance"
This reverts commit aec8a40228acb385d60feec59b54573d307e60f3. 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