Re: [PATCH v1 5/7] Revert "drm: Assert held reservation lock for dma-buf mmapping"

On 4/3/23 18:17, Christian König wrote: > Am 02.04.23 um 18:48 schrieb Dmitry Osipenko: >> Don't assert held dma-buf reservation lock on memory mapping of exported >> buffer. >> >> We're going to change dma-buf mmap() locking policy such that exporters >> will have to handle the lock. The previous

Re: [PATCH v1 5/7] Revert "drm: Assert held reservation lock for dma-buf mmapping"

Am 02.04.23 um 18:48 schrieb Dmitry Osipenko: Don't assert held dma-buf reservation lock on memory mapping of exported buffer. We're going to change dma-buf mmap() locking policy such that exporters will have to handle the lock. The previous locking policy caused deadlock problem for DRM drivers

[PATCH v1 5/7] Revert "drm: Assert held reservation lock for dma-buf mmapping"

Don't assert held dma-buf reservation lock on memory mapping of exported buffer. We're going to change dma-buf mmap() locking policy such that exporters will have to handle the lock. The previous locking policy caused deadlock problem for DRM drivers in a case of self-imported dma-bufs, it's solve