linux-kernel - Re: 2.6.18-mm1 compile failure on x86

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]

Date:	Tue, 26 Sep 2006 09:09:47 +0200
From:	Andi Kleen <ak@...e.de>
To:	Andrew Morton <akpm@...l.org>
Cc:	Martin Bligh <mbligh@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andy Whitcroft <apw@...dowen.org>
Subject: Re: 2.6.18-mm1 compile failure on x86_64

On Tuesday 26 September 2006 09:07, Andrew Morton wrote:
> On Tue, 26 Sep 2006 08:41:27 +0200
> Andi Kleen <ak@...e.de> wrote:
> 
> > On Tuesday 26 September 2006 00:39, Martin Bligh wrote:
> > > http://test.kernel.org/abat/49037/debug/test.log.0	
> > > 
> > >    AS      arch/x86_64/boot/bootsect.o
> > >    LD      arch/x86_64/boot/bootsect
> > >    AS      arch/x86_64/boot/setup.o
> > >    LD      arch/x86_64/boot/setup
> > >    AS      arch/x86_64/boot/compressed/head.o
> > >    CC      arch/x86_64/boot/compressed/misc.o
> > >    OBJCOPY arch/x86_64/boot/compressed/vmlinux.bin
> > > BFD: Warning: Writing section `.data.percpu' to huge (ie negative) file 
> > > offset 0x804700c0.
> > 
> > Most likely that is the problem. I don't know what patch it could be
> > (none of mine have been merged yet).
> 
> That was 2.6.18-mm1 - it has around 300 of "yours" ;)
> 
> > Can you bisect?
> 
> I was unable to reproduce it.  Lack of disk space is suspected.

I suppose the BFD warning (writing to negative file offset) will cause that.
I guess it tried to write ~4GB into the executable.

Probably it's a toolchain problem of some sort then.

-Andi


-
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/