linux-kernel - Re: 5.11-rc1 TTM list corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa11e930-d8ee-a291-7d6a-6fdd6653ffa8@amd.com>
Date:   Tue, 5 Jan 2021 16:40:16 +0100
From:   Christian König <christian.koenig@....com>
To:     Huang Rui <ray.huang@....com>, Borislav Petkov <bp@...en8.de>
Cc:     "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: 5.11-rc1 TTM list corruption

Am 05.01.21 um 13:20 schrieb Huang Rui:
> On Tue, Jan 05, 2021 at 07:43:51PM +0800, Borislav Petkov wrote:
>> On Tue, Jan 05, 2021 at 07:08:52PM +0800, Huang Rui wrote:
>>> Ah, this asic is a bit old and still use radeon driver. So we didn't
>>> reproduce it on amdgpu driver. I don't have such the old asic in my hand.
>>> May we know whether this issue can be duplicated after SI which is used
>>> amdgpu module (not sure whether you have recent APU or GPU)?
>> The latest I have (I think it is the latest) is:
>>
>> [    1.826102] [drm] initializing kernel modesetting (RENOIR 0x1002:0x1636 0x17AA:0x5099 0xD1).
>>
>> and so far that hasn't triggered it. Which makes sense because that
>> thing uses amdgpu:
>>
>> [    1.810260] [drm] amdgpu kernel modesetting enabled.
> Yes! Renoir is late enough for amdgpu kernel module. :-)
> Please let us know if you still encounter the issue.

Thanks for the hints guys. You need a rather specific configuration, but 
I can reproduce this now.

Let's see what the problem is here.

Thanks,
Christian.

>
> Thanks,
> Ray