new KASAN running piglit

[Christian König]

Going to investigate.

But any idea why the backtrace contains only "?" entries?

Christian.

Am 18.07.2018 um 18:09 schrieb Tom St Denis:
> Here's the dmesg I should have attached ...
>
> Tom
>
> On 07/18/2018 12:05 PM, Tom St Denis wrote:
>> Hi Christian,
>>
>> This patch:
>>
>> [root at raven linux]# git bisect bad
>> 90f362bdf0d0d06a126a5fd35b084436dd8250ad is the first bad commit
>> commit 90f362bdf0d0d06a126a5fd35b084436dd8250ad
>> Author: Christian König <christian.koenig at amd.com>
>> Date:   Mon Jul 16 14:58:48 2018 +0200
>>
>>      drm/amdgpu: change ring priority after pushing the job
>>
>>      Pushing a job can change the ring assignment of an entity.
>>
>>      Signed-off-by: Christian König <christian.koenig at amd.com>
>>      Reviewed-by: Chunming Zhou <david1.zhou at amd.com>
>>
>> :040000 040000 9a09d3e9d055e4f5024019861c334ee9cc0bd11b 
>> 522540c31c3d1a4f4a6fbac75e985e9a7f7e93c9 M      drivers
>>
>> causes a KASAN while running piglit.  It's reproduceable 100% of the 
>> time.  The commit before this doesn't not cause a KASAN.
>>
>> Tom