RE: [next-20250226]Build Failure

2025-03-01 Thread Michael Kelley
From: Kees Cook Sent: Friday, February 28, 2025 9:46 AM > > On Thu, Feb 27, 2025 at 03:15:35PM +0100, Christophe Leroy wrote: > > > > > > Le 27/02/2025 à 15:05, Michael Kelley a écrit : > > > From: Christophe Leroy Sent: Thursday, > > > February 27, 2025 2:43 AM > > > > > > > > Le 27/02/2025 à

Re: [next-20250226]Build Failure

2025-02-28 Thread Kees Cook
On Thu, Feb 27, 2025 at 03:15:35PM +0100, Christophe Leroy wrote: > > > Le 27/02/2025 à 15:05, Michael Kelley a écrit : > > From: Christophe Leroy Sent: Thursday, > > February 27, 2025 2:43 AM > > > > > > Le 27/02/2025 à 02:38, Stephen Rothwell a écrit : > > > > Hi Venkat, > > > > > > > > CC

Re: [next-20250226]Build Failure

2025-02-28 Thread Kees Cook
On Thu, Feb 27, 2025 at 03:15:35PM +0100, Christophe Leroy wrote: > > > Le 27/02/2025 à 15:05, Michael Kelley a écrit : > > From: Christophe Leroy Sent: Thursday, > > February 27, 2025 2:43 AM > > > > > > Le 27/02/2025 à 02:38, Stephen Rothwell a écrit : > > > > Hi Venkat, > > > > > > > > CC

Re: [next-20250226]Build Failure

2025-02-27 Thread Christophe Leroy
Le 27/02/2025 à 15:05, Michael Kelley a écrit : From: Christophe Leroy 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 mem

Re: [next-20250226]Build Failure

2025-02-27 Thread Christophe Leroy
Le 27/02/2025 à 14:47, Venkat Rao Bagalkote a écrit : Hello, Attached is the .config file. This is being run on IBM Power8 system in PowerVM mode, as a full system LPAR. Ah ok so you are using a quite old version of GCC, that is GCC 8.5 I get the same problem when building ppc64_defconf

RE: [next-20250226]Build Failure

2025-02-27 Thread Michael Kelley
From: Christophe Leroy 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 mor

Re: [next-20250226]Build Failure

2025-02-27 Thread Christophe Leroy
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 "C

Re: [next-20250226]Build Failure

2025-02-26 Thread Stephen Rothwell
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". On Thu, 27 Feb 202

[next-20250226]Build Failure

2025-02-26 Thread Venkat Rao Bagalkote
Greetings!!! I am seeing build failures with kernel next-20250226, on IBM Power8 systems. Failures: In file included from ./include/asm-generic/div64.h:27, from ./arch/powerpc/include/generated/asm/div64.h:1, from ./include/linux/math.h:6, from