linux-kernel - Re: 6.7/regression/KASAN: null-ptr-deref in amdgpu_ras_reset_error

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: <CABXGCsOKs33zOC-X7p5QOVWbSzDnSzuxAyGL-oxFBMVFx10pmQ@mail.gmail.com>
Date:   Wed, 15 Nov 2023 23:14:46 +0500
From:   Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To:     Alex Deucher <alexdeucher@...il.com>
Cc:     "Deucher, Alexander" <alexander.deucher@....com>,
        amd-gfx list <amd-gfx@...ts.freedesktop.org>,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        Christian König <christian.koenig@....com>
Subject: Re: 6.7/regression/KASAN: null-ptr-deref in amdgpu_ras_reset_error_count+0x2d6

On Wed, Nov 8, 2023 at 4:24 AM Mikhail Gavrilov
<mikhail.v.gavrilov@...il.com> wrote:
>
> Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
> Thanks, after applying the patch GPU loading meets expectations.
> Games are working so overall all looking good for now.
>

Unfortunately I didn't check this patch on 7900XTX.
And now I see that this patch leads the systems with 7900XTX GPU to a
lot of protection fault messages in the kernel log.

[   75.211702] gmc_v11_0_process_interrupt: 164 callbacks suppressed
[   75.211706] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault
(src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[   75.211715] amdgpu 0000:03:00.0: amdgpu:   in page starting at
address 0x00008087fe5fd000 from client 10
[   75.211718] amdgpu 0000:03:00.0: amdgpu:
GCVM_L2_PROTECTION_FAULT_STATUS:0x00041D53
[   75.211720] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: SDMA1 (0xe)
[   75.211723] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1
[   75.211725] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x1
[   75.211727] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5
[   75.211729] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1
[   75.211732] amdgpu 0000:03:00.0: amdgpu: RW: 0x1
[   75.211740] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault
(src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[   75.211743] amdgpu 0000:03:00.0: amdgpu:   in page starting at
address 0x00008087bffff000 from client 10
[   75.211746] amdgpu 0000:03:00.0: amdgpu:
GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[   75.211748] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0)
[   75.211750] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0
[   75.211752] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0
[   75.211754] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0
[   75.211756] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0
[   75.211758] amdgpu 0000:03:00.0: amdgpu: RW: 0x0
[   75.212337] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault
(src_id:0 ring:169 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[   75.212344] amdgpu 0000:03:00.0: amdgpu:   in page starting at
address 0x00008087fe5fd000 from client 10
[   75.212348] amdgpu 0000:03:00.0: amdgpu:
GCVM_L2_PROTECTION_FAULT_STATUS:0x00041B52
[   75.212352] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: SDMA0 (0xd)
[   75.212356] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0
[   75.212359] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x1
[   75.212363] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5
[   75.212367] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1
[   75.212370] amdgpu 0000:03:00.0: amdgpu: RW: 0x1

The full kernel log attached below.

-- 
Best Regards,
Mike Gavrilov.

Download attachment "dmesg-b13.zip" of type "application/zip" (165826 bytes)