linux-kernel - Re: Linux 6.6.70

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: <2025011058-mortify-decimal-96f6@gregkh>
Date: Fri, 10 Jan 2025 13:43:17 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Chris Clayton <chris2553@...glemail.com>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, stable@...r.kernel.org, lwn@....net,
	jslaby@...e.cz
Subject: Re: Linux 6.6.70

On Fri, Jan 10, 2025 at 08:51:33AM +0000, Chris Clayton wrote:
> On 09/01/2025 12:56, Greg Kroah-Hartman wrote:
> > I'm announcing the release of the 6.6.70 kernel.
> > 
> > All users of the 6.6 kernel series must upgrade.
> > 
> > The updated 6.6.y git tree can be found at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.6.y
> > and can be browsed at the normal kernel.org git web browser:
> > 	https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > ------------
> The build of stable 6.6.70 is failing on my config.
> 
> The error messages are:
> ld.bfd: kernel/kexec_core.o: in function `__crash_kexec':
> kexec_core.c:(.text+0x257): undefined reference to `machine_crash_shutdown'
> ld.bfd: kernel/kexec.o: in function `do_kexec_load':
> kexec.c:(.text+0x13e): undefined reference to `arch_kexec_protect_crashkres'
> ld.bfd: kexec.c:(.text+0x178): undefined reference to `arch_kexec_unprotect_crashkres'
> 
> My config file for building 6.6.x kernels is attached.
> 
> Happy to test a fix but please CC me because I'm not subscribed to LKML.

I think I have this fixed up now and will do a new release in a few
minutes with just this resolved.

thanks!

greg k-h