Re: [PATCH] drm/amdgpu: amdgpu_device_recover_vram got NULL of shadow->parent

Am 16.04.19 um 12:46 schrieb wentalou: amdgpu_bo_destroy had a bug by calling amdgpu_bo_unref outside mutex_lock. If amdgpu_device_recover_vram executed between amdgpu_bo_unref and list_del_init, it would get NULL of shadow->parent, then caused Call Trace and GPU reset failed. Change-Id:

[PATCH] drm/amdgpu: amdgpu_device_recover_vram got NULL of shadow->parent

amdgpu_bo_destroy had a bug by calling amdgpu_bo_unref outside mutex_lock. If amdgpu_device_recover_vram executed between amdgpu_bo_unref and list_del_init, it would get NULL of shadow->parent, then caused Call Trace and GPU reset failed. Change-Id: I41d7b54605e613e87ee03c3ad89c191063c19230

Re: [PATCH] drm/amdgpu: amdgpu_device_recover_vram got NULL of shadow->parent

Am 16.04.19 um 09:17 schrieb wentalou: amdgpu_bo_destroy had a bug by calling amdgpu_bo_unref outside mutex_lock. If amdgpu_device_recover_vram executed between amdgpu_bo_unref and list_del_init, it would get NULL of shadow->parent, then caused Call Trace and GPU reset failed. Change-Id:

[PATCH] drm/amdgpu: amdgpu_device_recover_vram got NULL of shadow->parent

amdgpu_bo_destroy had a bug by calling amdgpu_bo_unref outside mutex_lock. If amdgpu_device_recover_vram executed between amdgpu_bo_unref and list_del_init, it would get NULL of shadow->parent, then caused Call Trace and GPU reset failed. Change-Id: I41d7b54605e613e87ee03c3ad89c191063c19230