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]

Date:	Thu, 25 Jul 2013 10:53:53 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Tom Rini <trini@...com>
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 Wed, 2013-07-24 at 19:22 -0400, Tom Rini wrote:
> On 07/24/2013 05:05 PM, Paul Bolle wrote:
> > 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?

Won't v3.11-rc2 do?

> If so, I can take a peek took, if someone shoots me a config
> file.

The relevant config options should be CONFIG_NUMA and CONFIG_ACPI_NUMA
(both are bool, and set to 'y' in my .config).

But I've just pulled top-of-tree Linus, ie commit 07bc9dc1b0
("git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc'"). I'll
try to build that and I 'll send you my .config if this all is still
triggered.


Paul Bolle

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