diff options
| author | Nicolai Hähnle <[email protected]> | 2015-12-02 16:35:12 +0000 |
|---|---|---|
| committer | Alex Deucher <[email protected]> | 2015-12-02 20:04:04 +0000 |
| commit | 07df04dfcfe51a45239d056d43cbc09702262c82 (patch) | |
| tree | cd4cd9b9a9d38c1dd16ea31b11a4e87766b641b9 /drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | |
| parent | drm/amdgpu: add err check for pin userptr (diff) | |
| download | kernel-07df04dfcfe51a45239d056d43cbc09702262c82.tar.gz kernel-07df04dfcfe51a45239d056d43cbc09702262c82.zip | |
drm/amdgpu: fix race condition in amd_sched_entity_push_job
As soon as we leave the spinlock after the job has been added to the job
queue, we can no longer rely on the job's data to be available.
I have seen a null-pointer dereference due to sched == NULL in
amd_sched_wakeup via amd_sched_entity_push_job and
amd_sched_ib_submit_kernel_helper. Since the latter initializes
sched_job->sched with the address of the ring scheduler, which is
guaranteed to be non-NULL, this race appears to be a likely culprit.
Signed-off-by: Nicolai Hähnle <[email protected]>
Bugzilla: https://bugs.freedesktop.org/attachment.cgi?bugid=93079
Reviewed-by: Christian König <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_display.c')
0 files changed, 0 insertions, 0 deletions