On Wed, 26 Feb 2025 15:42:19 +0000, Brendan King wrote:
> Do scheduler queue fence release processing on a workqueue, rather
> than in the release function itself.
>
> Fixes deadlock issues such as the following:
>
> [ 607.400437] ============================================
> [ 607.405755] WARNING: possible recursive locking detected
> [ 607.415500] --------------------------------------------
> [ 607.420817] weston:zfq0/24149 is trying to acquire lock:
> [ 607.426131] ffff000017d041a0 (reservation_ww_class_mutex){+.+.}-{3:3}, at: pvr_gem_object_vunmap+0x40/0xc0 [powervr]
> [ 607.436728]
> but task is already holding lock:
> [ 607.442554] ffff000017d105a0 (reservation_ww_class_mutex){+.+.}-{3:3}, at: dma_buf_ioctl+0x250/0x554
> [ 607.451727]
> other info that might help us debug this:
> [ 607.458245] Possible unsafe locking scenario:
>
> [...]
Applied, thanks!
[1/1] drm/imagination: avoid deadlock on fence release
commit: df1a1ed5e1bdd9cc13148e0e5549f5ebcf76cf13
Best regards,
--
Matt Coster <matt.coster@xxxxxxxxxx>
