linux-kernel - Re: [next-20250226]Build Failure

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: <c68287f7-ad00-46fc-a92e-06e0c9074139@csgroup.eu>
Date: Thu, 27 Feb 2025 15:15:35 +0100
From: Christophe Leroy <christophe.leroy@...roup.eu>
To: Michael Kelley <mhklinux@...look.com>,
 Stephen Rothwell <sfr@...b.auug.org.au>,
 Venkat Rao Bagalkote <venkat88@...ux.vnet.ibm.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
 Kees Cook <kees@...nel.org>
Subject: Re: [next-20250226]Build Failure



Le 27/02/2025 à 15:05, Michael Kelley a écrit :
> From: Christophe Leroy <christophe.leroy@...roup.eu> Sent: Thursday, February 27, 2025 2:43 AM
>>
>> Le 27/02/2025 à 02:38, Stephen Rothwell a écrit :
>>> Hi Venkat,
>>>
>>> CC Kees Cook for advice.  This is a result of the tests added in commit
>>>
>>>     bbeb38b8487a ("string.h: Validate memtostr*()/strtomem*() arguments more carefully")
>>>
>>> from the kspp tree.
>>>
>>> I note that the comment about memtostr() says "Copy a possibly
>>> non-NUL-term string".
>>
>> Can you tell more about your config and your environment ?
>>
>> I just tested with ppc64_defconfig and ppc64le_defconfig, with gcc 12.4,
>> gcc 13.2 and gcc 14.2 and didn't get that build error.
>>
>> Christophe
> 
> FWIW, I see the same build failures related to __must_be_noncstr()
> when building natively on x86 and on arm64. In both cases, it's an
> Ubuntu 20.04 installation with gcc 9.4.0 and binutils 2.34.
> 

Looks like I get that problem only with GCC 8.5 and GCC 9.5.

I don't get it with gcc 10.3 nor 11.3 nor 12.4 nor 13.2 nor 14.2
I don't get it either with gcc 5.5 or 7.5

Christophe