summaryrefslogtreecommitdiff
path: root/include/dt-bindings/power/r8a7794-sysc.h
diff options
context:
space:
mode:
authorXiaohui Zhang <xiaohuizhang@ruc.edu.cn>2022-06-07 18:19:33 +0300
committerAlex Deucher <alexander.deucher@amd.com>2022-06-08 18:41:09 +0300
commit0381ac3ca2e727d4dfb7264d9416a8ba6bb6c18b (patch)
tree0cab399e9047754dc2415a618ee7033f71dc2ead /include/dt-bindings/power/r8a7794-sysc.h
parent4e2d10443580d934188f226f48eda7d650711e03 (diff)
downloadlinux-0381ac3ca2e727d4dfb7264d9416a8ba6bb6c18b.tar.xz
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 'include/dt-bindings/power/r8a7794-sysc.h')
0 files changed, 0 insertions, 0 deletions