;
maarten.lankho...@linux.intel.com; Thomas Hellström
; Ruhl; Ruhl, Michael J
Subject: [PATCH v3 4/5] drm/i915/gem: Fix same-driver-another-instance
dma-buf export
If our exported dma-bufs are imported by another instance of our driver,
that instance will typically have the imported dma-bufs locked during
gt;maarten.lankho...@linux.intel.com; Thomas Hellström
> >; Ruhl; Ruhl, Michael J
> >
> >Subject: [PATCH v3 4/5] drm/i915/gem: Fix same-driver-another-instance
> >dma-buf export
> >
> >If our exported dma-bufs are imported by another instance of our driver,
ct: [PATCH v3 4/5] drm/i915/gem: Fix same-driver-another-instance
>dma-buf export
>
>If our exported dma-bufs are imported by another instance of our driver,
>that instance will typically have the imported dma-bufs locked during
>map_attachment(). But the exporter also locks the s
If our exported dma-bufs are imported by another instance of our driver,
that instance will typically have the imported dma-bufs locked during
map_attachment(). But the exporter also locks the same reservation
object in the map_dma_buf() callback, which leads to recursive locking.
Add a live selft
