linux-kernel - Re: Blackfin link issue (Was: linux-next: triage for March 27, 2012)

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: <20120328002359.GA12442@windriver.com>
Date:	Tue, 27 Mar 2012 20:23:59 -0400
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Mike Frysinger <vapier.adi@...il.com>,
	Bob Liu <lliubbo@...il.com>
Subject: Re: Blackfin link issue (Was: linux-next: triage for March 27, 2012)

[Blackfin link issue (Was: linux-next: triage for March 27, 2012)] On 28/03/2012 (Wed 11:03) Stephen Rothwell wrote:

> Hi Paul,
> 
> On Tue, 27 Mar 2012 17:36:27 -0400 Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> >
> > The blackfin builds are no longer failing on vm_is_stack but instead
> > are all failing with "L1 data A overflow!" at final link, which smells
> > like some kind of binutils/toolchain issue.
> > 
> > 
> > bfin:***all-builds***
> > 	when:	Mar 26
> > 	why:	bfin-uclinux-ld: L1 data A overflow!
> > 	status:	unknown, binutils issue?
> > 	fix:
> > 	ref:	http://kisskb.ellerman.id.au/kisskb/buildresult/5981475/
> 
> It actually looks like this comes from an ASSERT in the blackfin
> vmlinux.lds.S ... looks like some sections overflowed.

Thanks Stephen -- I see you've CC'd some blackfin folks -- lets hope
they can help shed some light on this.  I'll admit my guess above
was only that --- just a guess.

Paul.
--

> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au


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