linux-kernel - Re: linux-next-20251029

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: <1296761.1762045181@turing-police>
Date: Sat, 01 Nov 2025 20:59:41 -0400
From: "Valdis KlÄ“tnieks" <valdis.kletnieks@...edu>
To: Timur KristÃ³f <timur.kristof@...il.com>
cc: Alex Deucher <alexander.deucher@....com>,
    Leo Li <sunpeng.li@....com>, David Airlie <airlied@...il.com>,
    amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
    linux-kernel@...r.kernel.org
Subject: Re: linux-next-20251029 - build error in amdgpu

On Thu, 30 Oct 2025 19:05:30 +0100, Timur Kristóf said:

> Can you say how to reproduce that?
> I use the same version of GCC but it hasn't given me any warning or
> error for that patch.

Upon further testing, 

[/usr/src/linux-next] make 

is sufficient on my system. Turns out that it errors out even without W=1. My
next guess was that it had to do with -Werror, which would cause warnings to
be treated as errors, but my .config has

# CONFIG_WERROR is not set
# CONFIG_DRM_WERROR is not set
# CONFIG_DRM_AMDGPU_WERROR is not set

Do you perhaps have patches in your tree that aren't in next-20251029?

I wonder if Fedora's build of gcc 15.2.1 is different somehow from the
build you're using....

........