linux-kernel - Re: evergreen_packet3_check:... radeon 0000:1d:00.0: vbo resource seems too big for the bo

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] [day] [month] [year] [list]

Message-ID: <0671680b-842f-4771-ade5-2485c9a91356@mailbox.org>
Date: Wed, 10 Sep 2025 10:12:16 +0200
From: Michel Dänzer <michel.daenzer@...lbox.org>
To: Christian König <christian.koenig@....com>,
 Alex Deucher <alexdeucher@...il.com>, Borislav Petkov <bp@...en8.de>
Cc: amd-gfx@...ts.freedesktop.org, Alex Deucher <alexander.deucher@....com>,
 dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: evergreen_packet3_check:... radeon 0000:1d:00.0: vbo resource
 seems too big for the bo

On 10.09.25 10:02, Christian König wrote:
> On 09.09.25 18:21, Alex Deucher wrote:
>> On Tue, Sep 9, 2025 at 12:17 PM Borislav Petkov <bp@...en8.de> wrote:
>>>
>>> On Tue, Sep 09, 2025 at 10:43:47AM +0200, Michel Dänzer wrote:
>>>> Then the developer needs to tell the user how to enable the debugging output
>>>> and get it to them. That's pretty standard.
>>>
>>> *IF* the user even notices anything. As said earlier, it didn't cause any
>>> anomalies on my machine besides flooding dmesg. Which I look at for obvious
>>> reasons but users probably don't.
>>
>> Right.  I think there needs to be something otherwise no one will notice at all.
> 
> Well doesn't the cause of the warning result in corrupted rendering?

Per https://gitlab.freedesktop.org/mesa/mesa/-/issues/13838#note_3088335 it would result in one dropped vertex, which might be hard to notice. That's why I agree that in this specific case, not logging anything by default might have resulted in the issue taking much longer to be discovered (if ever).

(A potential counter argument being: If it's not noticeable, does the kernel need to log anything about it by default?)

-- 
Earthling Michel Dänzer       \        GNOME / Xwayland / Mesa developer
https://redhat.com             \               Libre software enthusiast