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:15 +0000
committerThomas Zimmermann <[email protected]>2025-07-17 10:26:19 +0000
commit2712ca878b688682ac2ce02aefc413fc76019cd9 (patch)
tree04c899bb9a1b1163cfa32c4071f2c3ebdf0148e8 /drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
parentRevert "drm/prime: Use dma_buf from GEM object instance" (diff)
downloadkernel-2712ca878b688682ac2ce02aefc413fc76019cd9.tar.gz
kernel-2712ca878b688682ac2ce02aefc413fc76019cd9.zip
Revert "drm/gem-framebuffer: Use dma_buf from GEM object instance"
This reverts commit cce16fcd7446dcff7480cd9d2b6417075ed81065. 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. v3: - cc stable 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]> Cc: <[email protected]> # v6.15+ 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