linux-kernel - Re: [tip: x86/build] x86/boot: Drop CRC-32 checksum and the build tool that generates it

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <364ad671-5e5c-47c1-af22-34a7c481f8e3@intel.com>
Date: Fri, 11 Apr 2025 12:33:47 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org
Cc: Ard Biesheuvel <ardb@...nel.org>, Ingo Molnar <mingo@...nel.org>,
 "H. Peter Anvin" <hpa@...or.com>, Ian Campbell <ijc@...lion.org.uk>,
 Linus Torvalds <torvalds@...ux-foundation.org>, x86@...nel.org
Subject: Re: [tip: x86/build] x86/boot: Drop CRC-32 checksum and the build
 tool that generates it

On 3/7/25 15:11, tip-bot2 for Ard Biesheuvel wrote:
> x86/boot: Drop CRC-32 checksum and the build tool that generates it

This is breaking really early boot for me across a whole bunch of i386
and 64-bit builds. I had to bisect it because this does not seem like
the kind of thing that would break the boot. It's either hanging the
kernel *really* early, or making KVM angry:

KVM internal error. Suberror: 1
extra data[0]: 0x0000000000000000
extra data[1]: 0x0000000000000030
extra data[2]: 0x0000000000000784
extra data[3]: 0x0000000000000000
extra data[4]: 0x0000000000000000
extra data[5]: 0x0000000000000000
emulation failure
EAX=00000000 EBX=00000000 ECX=00000000 EDX=00083238
ESI=00000000 EDI=00000000 EBP=00000000 ESP=0000fff5
EIP=00008300 EFL=00010002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
...

I'm going to go start backing out individual hunks like the
arch/x86/boot/compressed/vmlinux.lds.S changes, but I figured I'd see if
anyone else is having problems or has more of a clue than I do.

The only weird thing I'm doing is booting the kernel with qemu's -kernel
argument.