Re: [PATCH] drm/panfrost: Make sure a BO is only unmapped when appropriate

2019-06-01 Thread Boris Brezillon
On Fri, 31 May 2019 14:54:54 +0200 Tomeu Vizoso wrote: > On Wed, 29 May 2019 at 11:18, Boris Brezillon > wrote: > > > > mmu_ops->unmap() will fail when called on a BO that has not been > > previously mapped, and the error path in panfrost_ioctl_create_bo() > > can call drm_gem_object_put_unlocke

Re: [PATCH] drm/panfrost: Make sure a BO is only unmapped when appropriate

2019-05-31 Thread Tomeu Vizoso
On Wed, 29 May 2019 at 11:18, Boris Brezillon wrote: > > mmu_ops->unmap() will fail when called on a BO that has not been > previously mapped, and the error path in panfrost_ioctl_create_bo() > can call drm_gem_object_put_unlocked() (which in turn calls > panfrost_mmu_unmap()) on a BO that has not

[PATCH] drm/panfrost: Make sure a BO is only unmapped when appropriate

2019-05-29 Thread Boris Brezillon
mmu_ops->unmap() will fail when called on a BO that has not been previously mapped, and the error path in panfrost_ioctl_create_bo() can call drm_gem_object_put_unlocked() (which in turn calls panfrost_mmu_unmap()) on a BO that has not been mapped yet. Keep track of the mapped/unmapped state to av