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]
Date: Sat, 1 Jun 2024 07:39:25 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
	lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
	f.fainelli@...il.com, sudipm.mukherjee@...il.com,
	srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
	allen.lkml@...il.com, broonie@...nel.org
Subject: Re: [PATCH 6.8 000/493] 6.8.12-rc1 review

On Fri, May 31, 2024 at 01:27:44PM -0700, Guenter Roeck wrote:
> On 5/27/24 11:50, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.8.12 release.
> > There are 493 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Wed, 29 May 2024 18:53:22 +0000.
> > Anything received after that time might be too late.
> > 
> 
> Build failures in v6.8.12:
> 
> Building csky:allmodconfig ... failed
> Building m68k:allmodconfig ... failed
> Building xtensa:allmodconfig ... failed
> 
> --------------
> Error log:
> In file included from kernel/sched/build_utility.c:104:
> kernel/sched/isolation.c: In function 'housekeeping_setup':
> kernel/sched/isolation.c:134:53: error: 'setup_max_cpus' undeclared (first use in this function)
>   134 |         if (first_cpu >= nr_cpu_ids || first_cpu >= setup_max_cpus) {
> 
> Commit 3c2f8859ae1ce ("smp: Provide 'setup_max_cpus' definition on UP too")
> might solve the problem.

Thanks for the report, but 6.8.y is now end-of-life :(

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ