linux-kernel - Re: [PATCH 3/3] Revert "hardening: Disable GCC randstruct for COMPILE

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: <20250530190904.GA1159814@ax162>
Date: Fri, 30 May 2025 12:09:04 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Kees Cook <kees@...nel.org>
Cc: Thiago Jung Bauermann <thiago.bauermann@...aro.org>,
	akpm@...ux-foundation.org, arnd@...db.de, broonie@...nel.org,
	davidgow@...gle.com, diego.daniel.professional@...il.com,
	gnoack@...gle.com, gustavoars@...nel.org, jmorris@...ei.org,
	justinstitt@...gle.com, linux-hardening@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org,
	linux@...blig.org, llvm@...ts.linux.dev, mcgrof@...nel.org,
	mic@...ikod.net, morbo@...gle.com, nick.desaulniers+lkml@...il.com,
	paul@...l-moore.com, pmladek@...e.com, rmoar@...gle.com,
	serge@...lyn.com, tamird@...il.com, wangyuli@...ontech.com
Subject: Re: [PATCH 3/3] Revert "hardening: Disable GCC randstruct for
 COMPILE_TEST"

On Thu, May 29, 2025 at 10:12:22PM -0700, Kees Cook wrote:
> On Thu, May 29, 2025 at 09:06:46PM -0300, Thiago Jung Bauermann wrote:
> > This commit was reported by our CI as breaking the allmodconfig build for
> > the arm and arm64 architectures when using GCC 15. This is due to
> > https://github.com/KSPP/linux/issues/367 :
> > 
> > 00:05:08 arch/arm64/kernel/kexec_image.c:132:14: internal compiler error: in comptypes_check_enum_int, at c/c-typeck.cc:1519
> > 00:05:08   132 | const struct kexec_file_ops kexec_image_ops = {
> > 00:05:08       |              ^~~~~~~~~~~~~~
> 
> I'm not able to reproduce this. Which specific version of GCC 15 and
> on what distro are you seeing this?

It looks like this was also reported to Debian (I originally noticed it
in the #gcc channel on OFTC a couple of weeks ago but forgot to mention
it):

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104745

It looks like the difference might be whether GCC was built with
additional checks or not based on the last couple of comments in that
bug.

Cheers,
Nathan