diff options
| author | Thomas Zimmermann <[email protected]> | 2025-07-15 15:58:14 +0000 |
|---|---|---|
| committer | Thomas Zimmermann <[email protected]> | 2025-07-17 10:26:19 +0000 |
| commit | fb4ef4a52b79a22ad382bfe77332642d02aef773 (patch) | |
| tree | b073695a93328b00e916247e8af2d8e959f59073 /drivers/gpio/gpio-mpc5200.c | |
| parent | Revert "drm/etnaviv: Use dma_buf from GEM object instance" (diff) | |
| download | kernel-fb4ef4a52b79a22ad382bfe77332642d02aef773.tar.gz kernel-fb4ef4a52b79a22ad382bfe77332642d02aef773.zip | |
Revert "drm/prime: Use dma_buf from GEM object instance"
This reverts commit f83a9b8c7fd0557b0c50784bfdc1bbe9140c9bf8.
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/gpio/gpio-mpc5200.c')
0 files changed, 0 insertions, 0 deletions
