linux-kernel - Re: Section conflicts with percpu variables

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

Date:	Thu, 28 Oct 2010 11:21:33 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Xen-devel@...ts.xensource.com" <Xen-devel@...ts.xensource.com>,
	Teck Choon Giam <giamteckchoon@...il.com>
Subject: Re: Section conflicts with percpu variables

On 10/27/2010 09:05 PM, Jeremy Fitzhardinge wrote:
>  Hi Tejun,
> 
> I wonder if you could have a look at this.  I have someone reporting
> compilation failures when using the stock Centos 5 compiler:
> 
> arch/x86/xen/mmu.c:163: error: __pcpu_scope_xen_cr3 causes a section type conflict
> arch/x86/xen/mmu.c:164: error: __pcpu_scope_xen_current_cr3 causes a section type conflict
> arch/x86/xen/mmu.c:163: error: __pcpu_unique_xen_cr3 causes a section type conflict
> arch/x86/xen/mmu.c:164: error: __pcpu_unique_xen_current_cr3 causes a section type conflict
> 
> Looking at mmu.i, I can't see why it is picking on these particular
> per-cpu variables.  Do you have any insight into this.

Hmmm... me neither.  section type conflict?  Does it make any
different if you move the definitions near the top of the file or use
a different compiler version?

Thanks.

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