drm/ttm: use reservation_object_trylock in ttm_bo_individualize_resv
Subsystems (3)
PATCH 1/1 drm/ttm: use reservation_object_trylock in ttm_bo_individualize_resv
From: Christian König <[email protected]>
Fixes a false positive from might_sleep(). The reservation object is freshly initialized, so nobody else can hold the mutex but the function is called from atomic context.
Signed-off-by Christian König <[email protected]>
--- drivers/gpu/drm/ttm/ttm_bo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/ttm/ttm_bo.c +1 -1
@@ -403,7 +403,7 @@ static int ttm_bo_individualize_resv(struct ttm_buffer_object *bo)return 0 ;reservation_object_init (&bo->ttm_resv); -BUG_ON (reservation_object_lock (&bo->ttm_resv,NULL )); +BUG_ON (reservation_object_trylock (&bo->ttm_resv)); r =reservation_object_copy_fences (&bo->ttm_resv, bo->resv);if (r) {
Signature · 6 lines
2.7.4 _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx