linux-kernel - Re: compile 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]

Message-ID: <51F061CC.9080704@ti.com>
Date:	Wed, 24 Jul 2013 19:22:52 -0400
From:	Tom Rini <trini@...com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	Jianpeng Ma <majianpeng@...il.com>,
	Rusty Russell <rusty@...tcorp.com.au>, <tglx@...utronix.de>,
	<x86@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: compile x86_64 waring

On 07/24/2013 05:05 PM, Paul Bolle wrote:
> [Added Tom and Rusty because they might be able to say what's really
> going on here.]
> 
> On Fri, 2013-07-05 at 19:56 +0800, majianpeng wrote:
>> Compile x86_64 meet those messages:
>> WARNING: arch/x86/mm/built-in.o(.text.unlikely+0xbf8): Section mismatch in reference from the function __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
>> The function __node_set.constprop.0() references
>> the variable __initdata numa_nodes_parsed.
>> This is often because __node_set.constprop.0 lacks a __initdata 
>> annotation or the annotation of numa_nodes_parsed is wrong.
>>
>> WARNING: arch/x86/built-in.o(.text.unlikely+0x171d): Section mismatch in reference from the function __node_set.constprop.0() to the variable .init.data:numa_nodes_parsed
>> The function __node_set.constprop.0() references
>> the variable __initdata numa_nodes_parsed.
>> This is often because __node_set.constprop.0 lacks a __initdata 
>> annotation or the annotation of numa_nodes_parsed is wrong.
> 
> 0) I noticed these too, on v3.11-rc1 and v3.12.-rc2. I assume Jianpeng
> Ma reported these for a linux-next release that preceded v3.11-rc1.
> 
> 1) The only hits for node_set and numa_nodes_parsed in arch/x86/mm are
> in amdtopology.c, numa.c, and srat.c. If I peek at the object files
> generated for these three files I notice that numa.o and srat.o have
> node_set() in their .text.unlikely section. (amdtopology.o doesn't have
> a .text.unlikely section.) 
> 
> 2) I guess that since commit 06df44ee41442d83be061c5fd1b1de4f5fc6fbbf
> ("modpost.c: Add .text.unlikely to TEXT_SECTIONS"), which was included
> in v3.11-rc1, code in .text.unlikely sections generates a mismatch
> warning if it references __initdata code (and numa_nodes_parsed is
> __initdata). But all calls of node_set() in these two files are from
> within functions that are marked __init. And I think references from
> __init code to __initdata code shouldn't lead to mismatch warnings,
> should they?
> 
> 3) So this looks like a false positive to me (but I'm not at all
> familiar with, well, the section mismatch checks). Would there be a way
> to silence this warning? Other than dropping __initdata from
> numa_nodes_parsed, of course.

I suspect you have a real problem, in that either numa_nodes_parsed
needs to not be __initdata (as it's being called by both __init and
non-__init functions, and hence the problem), or the other caller(s) of
numa_nodes_parsed need to also be __init.  Is this seen in top-of-tree
Linus?  If so, I can take a peek took, if someone shoots me a config
file.  Thanks!

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