diff options
author | 2025-07-15 10:45:39 +0200 | |
---|---|---|
committer | 2025-08-26 10:41:27 +0200 | |
commit | 16fdb3cc6af8460f23a706512c6f5e7dfdd4f338 (patch) | |
tree | 095f7ea95786aba619a23a4cdae2bfe2e7493156 /tools/perf/scripts/python | |
parent | drm/gpuvm: fix various typos in .c and .h gpuvm file (diff) | |
download | wireguard-linux-16fdb3cc6af8460f23a706512c6f5e7dfdd4f338.tar.xz wireguard-linux-16fdb3cc6af8460f23a706512c6f5e7dfdd4f338.zip |
Revert "drm/tegra: Use dma_buf from GEM object instance"
This reverts commit 482c7e296edc0f594e8869a789a40be53c49bd6a.
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>
Link: https://lore.kernel.org/r/20250715084549.41473-1-tzimmermann@suse.de
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions