diff options
author | Thomas Zimmermann <tzimmermann@suse.de> | 2025-07-15 17:58:12 +0200 |
---|---|---|
committer | Thomas Zimmermann <tzimmermann@suse.de> | 2025-07-17 12:26:19 +0200 |
commit | 1e9d2aed7c2248bc5ba7d0dfea4fcc0b2f80b4f7 (patch) | |
tree | fb2cabe5319d18514e0aa47f3bae97f544f25dcf /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | 0ecfb8ddb953605cadd806de5b62e632c8e0e49e (diff) |
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 <tzimmermann@suse.de>
Reviewed-by: Simona Vetter <simona.vetter@ffwll.ch>
Acked-by: Christian König <christian.koenig@amd.com>
Acked-by: Zack Rusin <zack.rusin@broadcom.com>
Link: https://lore.kernel.org/r/20250715155934.150656-3-tzimmermann@suse.de
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions