linux-kernel - Re: commit 6520fe5564acf07ade7b18a1272db1184835c487 "x86, realmode: 16-bit real-mode code support for relocs tool" breaks cross-compilation from x86-64 -> x86-32

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>] [day] [month] [year] [list]

Message-ID: <4FB914A6.2000809@linux.intel.com>
Date:	Sun, 20 May 2012 08:58:30 -0700
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	Arthur Marsh <arthur.marsh@...ernode.on.net>
CC:	Jarkko Sakkinen <jarkko.sakkinen@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: commit 6520fe5564acf07ade7b18a1272db1184835c487 "x86, realmode:
 16-bit real-mode code support for relocs tool" breaks cross-compilation from
 x86-64 -> x86-32

On 05/20/2012 04:38 AM, Arthur Marsh wrote:
> Hi, I normally use the make-kpkg script on Debian unstable on an AMD64
> machine to rebuild 32-bit x86 kernels via the following command line:
> 
> CONCURRENCY_LEVEL=8 DEB_HOST_ARCH=i386 \
> MAKEFLAGS="CC=gcc-4.7 LD=ld.gold" make-kpkg \
> --initrd --config menuconfig --arch i386 \
> --cross-compile - linux-image
> 
> This failed recently with the output:
> 
> 
> Is this a problem with the Debian mk-kpkg command from kernel-package or
> the kernel's own build system?
> 

Neither.  It means you have exposed a linker bug.  It was believed to be
only in GNU ld, but apparently it is in gold as well (building the
kernel with gold has always been iffy.)

The bisect isn't very useful, because you really want the result from
two patches later.

Let me emphasize: these patches only *detect* the failure, turning it
from silent corruption to an error message.

	-hpa


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/