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:11 +0000
committerThomas Zimmermann <[email protected]>2025-07-17 10:26:19 +0000
commit0ecfb8ddb953605cadd806de5b62e632c8e0e49e (patch)
tree5e2d3e57cade4d6de23aab7d8d4a5f0fb322a41e /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
parentdrm/sched: Remove optimization that causes hang when killing dependent jobs (diff)
downloadkernel-0ecfb8ddb953605cadd806de5b62e632c8e0e49e.tar.gz
kernel-0ecfb8ddb953605cadd806de5b62e632c8e0e49e.zip
Revert "drm/virtio: Use dma_buf from GEM object instance"
This reverts commit 415cb45895f43015515473fbc40563ca5eec9a7c. 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