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 18:36:38 +0000 (14:36 -0400)
commitcfadd5a936d00312998c769ee48e64970692835a
treedd276b1054ffbf372c39bce8a94774a44a7fbf7d
parent6e3fe4eaabe706619b5805dde221aaedbcb9c8bf
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