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: <20250901101011.GAaLVxA_Ax0R-Wy2IX@fat_crate.local>
Date: Mon, 1 Sep 2025 12:10:11 +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 01, 2025 at 11:27:01AM +0200, Michel Dänzer wrote:
> use some kind of debug output API which doesn't hit dmesg by default

You still want to be enabled by default so that normal users can see it and
actually report it.

> (can be a non-once variant instead, that's more useful for user-space
> developers).

I don't see how a non-once variant can tell you anything new - it is repeating
one cryptic message to most users so what's the point of parroting it more
than once?

IMO, that message should be beefed up to have more information, dump it once
and encourage users to report it.

Then, whoever gets to debug it, will ask for a reproducer and then do their
own kernel patching to add more info and make the message more useful to them
when debugging the thing.

At least this is how I would do it...

-- 
Regards/Gruss,
    Boris.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ