diff options
| author | Xiaohui Zhang <xiaohuizhang@ruc.edu.cn> | 2022-06-07 23:19:33 +0800 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2022-06-08 11:41:09 -0400 |
| commit | 0381ac3ca2e727d4dfb7264d9416a8ba6bb6c18b (patch) | |
| tree | 0cab399e9047754dc2415a618ee7033f71dc2ead /scripts/objdiff | |
| parent | drm/amdkfd: Document and fix GTT BO kmap API (diff) | |
| download | linux-0381ac3ca2e727d4dfb7264d9416a8ba6bb6c18b.tar.gz linux-0381ac3ca2e727d4dfb7264d9416a8ba6bb6c18b.zip | |
drm/radeon: Initialize fences array entries in radeon_sa_bo_next_hole
Similar to the handling of amdgpu_sa_bo_next_hole in commit 6a15f3ff19a8
("drm/amdgpu: Initialize fences array entries in amdgpu_sa_bo_next_hole"),
we thought a patch might be needed here as well.
The entries were only initialized once in radeon_sa_bo_new. If a fence
wasn't signalled yet in the first radeon_sa_bo_next_hole call, but then
got signalled before a later radeon_sa_bo_next_hole call, it could
destroy the fence but leave its pointer in the array, resulting in
use-after-free in radeon_sa_bo_new.
Signed-off-by: Xiaohui Zhang <xiaohuizhang@ruc.edu.cn>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions