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

Message-ID: <20250908180022.GHaL8Zto-PsVsPa0e0@fat_crate.local>
Date: Mon, 8 Sep 2025 20:00:22 +0200
From: Borislav Petkov <bp@...en8.de>
To: Michel Dänzer <michel.daenzer@...lbox.org>
Cc: Alex Deucher <alexdeucher@...il.com>, amd-gfx@...ts.freedesktop.org,
	Alex Deucher <alexander.deucher@....com>,
	Christian König <christian.koenig@....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 Mon, Sep 08, 2025 at 07:05:17PM +0200, Michel Dänzer wrote:
> These messages are primarily intended for developers, not users

But everybody sees them! And they're flooding the console.

And most people seeing them are users, not developers.

And if those messages are only for developers, they better be not visible by
default but behind a CONFIG_DEBUG or a similar switch.

And developers don't have every hw to test on. So you need to rely on users to
report issues to you. Because those messages probably don't fire on your hw
but someone else would hit them. And the chances are high that someone else is
a user.

So you want to make *all* your messages for users and have them report them
back to you.

> (which will notice and report the corresponding user-space issues instead).

The case due to which we're having this conversation didn't manifest itself
into anything - it was only flooding my dmesg. So users will notice nothing.

> The once variant means user-space developers need to reboot after hitting it
> once.

/sys/kernel/debug/clear_warn_once

Although when I tried it, it didn't help with dev_warn_once(). Perhaps needs
adding.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette