diff options
author | 2024-12-06 13:17:45 +0100 | |
---|---|---|
committer | 2024-12-18 12:16:35 -0500 | |
commit | 2ae520cb12831d264ceb97c61f72c59d33c0dbd7 (patch) | |
tree | d8d927a0c8e39a9ce2f6a8453a60cbce008efaf3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | drm/amd/display: use swap() in update_phy_id_mapping() (diff) | |
download | wireguard-linux-2ae520cb12831d264ceb97c61f72c59d33c0dbd7.tar.xz wireguard-linux-2ae520cb12831d264ceb97c61f72c59d33c0dbd7.zip |
drm/amdgpu: don't access invalid sched
Since 2320c9e6a768 ("drm/sched: memset() 'job' in drm_sched_job_init()")
accessing job->base.sched can produce unexpected results as the initialisation
of (*job)->base.sched done in amdgpu_job_alloc is overwritten by the
memset.
This commit fixes an issue when a CS would fail validation and would
be rejected after job->num_ibs is incremented. In this case,
amdgpu_ib_free(ring->adev, ...) will be called, which would crash the
machine because the ring value is bogus.
To fix this, pass a NULL pointer to amdgpu_ib_free(): we can do this
because the device is actually not used in this function.
The next commit will remove the ring argument completely.
Fixes: 2320c9e6a768 ("drm/sched: memset() 'job' in drm_sched_job_init()")
Signed-off-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions