On Wed, Dec 2, 2015 at 8:18 AM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> 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_sc
From: Nicolai Hähnle
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_ker
