linux-kernel - Re: Please include const-sections into linux-next

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: <1318799006.2995.1.camel@dabdike.int.hansenpartnership.com>
Date:	Sun, 16 Oct 2011 16:03:26 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: Please include const-sections into linux-next

On Sun, 2011-10-16 at 05:35 +0200, Andi Kleen wrote:
> > I have no idea why, though.
> 
> Thanks for testing.
> 
> Yes it's hard to tell with plain gcc (before 4.7)
> I have a special gcc patch to tell me the other symbol :)
> 
> Usually it's because some other symbol is wrong. In this 
> case it must be in the same translation unit.
> 
> Can you please do
> 
> make mm/percpu.i 
> 
> on that build and send me the percpu.i in private email?

OK, so after fixing up that one, the next failure is:

drivers/net/fealnx.c:95: error: version causes a section type conflict
drivers/net/fealnx.c:1944: error: fealnx_pci_tbl causes a section type conflict

James


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