search for: dma_buf_mmap_intern

...lock. The current dma-buf locking policy > claims that importer holds the lock for mmap(), but DRM code assumes > that obj->mmap() handles the locking itself and then the same > obj->mmap() code path is used by both dma-buf DRM and a usual DRM object > paths. Hence importer -> dma_buf_mmap_internal()[takes the lock] -> > exporter -> drm_gem_shmem_mmap()[takes the lock] deadlocks. > > I was looking at how to fix it and to me the best option is to change > the dma-buf locking policy, making exporter responsible for handling the > resv lock. Changing DRM code mmap lockings...