kmssink: Don't leak GEM primed from DMABuf
authorNicolas Dufresne <nicolas.dufresne@collabora.com>
Thu, 6 Jul 2017 21:20:56 +0000 (17:20 -0400)
committerNicolas Dufresne <nicolas.dufresne@collabora.com>
Fri, 7 Jul 2017 19:49:24 +0000 (15:49 -0400)
commite1c02e097d671c454e5e3afdad3c96b1eedebaf5
treedff91143b101047597084b55bff7875610ff8c5e
parent8f7ce6bc6aa0730935f78dba2c21d0d0ee79f18f
kmssink: Don't leak GEM primed from DMABuf

This otherwise breaks DMABuf reclaiming. This is not visible from
userspace, but inside the kernel, the DRM driver will hold a ref to the
DMABuf object. With a V4L2 driver allocating those DMABuf, it then
prevent changing the resolution and re-allocation new buffers.

https://bugzilla.gnome.org/show_bug.cgi?id=782774
sys/kms/gstkmsallocator.c