Revision 07df04dfcfe51a45239d056d43cbc09702262c82 authored by Nicolai Hähnle on 02 December 2015, 16:35:12 UTC, committed by Alex Deucher on 02 December 2015, 20:04:04 UTC
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 <nicolai.haehnle@amd.com> Bugzilla: https://bugs.freedesktop.org/attachment.cgi?bugid=93079 Reviewed-by: Christian König <christian.koenig@amd.com>
1 parent e2f784f
Computing file changes ...
