diff options
| author |   Chris Wilson <chris@chris-wilson.co.uk> | 2017-08-19 13:05:58 +0100 |
|---|---|---|
| committer |   Joonas Lahtinen <joonas.lahtinen@linux.intel.com> | 2017-08-22 16:03:43 +0300 |
| commit | fe4600a548f2763dec91b3b27a1245c370ceee2a (patch) | |
| tree | aa34827d35580d03bebbb1dad9bf0483e5e80242 /drivers/gpu/drm/bridge | |
| parent | drm/atomic: If the atomic check fails, return its value first (diff) | |
| download | linux-dev-fe4600a548f2763dec91b3b27a1245c370ceee2a.tar.xz linux-dev-fe4600a548f2763dec91b3b27a1245c370ceee2a.zip | |
drm: Release driver tracking before making the object available again
This is the same bug as we fixed in commit f6cd7daecff5 ("drm: Release
driver references to handle before making it available again"), but now
the exposure is via the PRIME lookup tables. If we remove the
object/handle from the PRIME lut, then a new request for the same
object/fd will generate a new handle, thus for a short window that
object is known to userspace by two different handles. Fix this by
releasing the driver tracking before PRIME.
Fixes: 0ff926c7d4f0 ("drm/prime: add exported buffers to current fprivs
imported buffer list (v2)")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Thierry Reding <treding@nvidia.com>
Cc: stable@vger.kernel.org
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20170819120558.6465-1-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/bridge')
0 files changed, 0 insertions, 0 deletions