linux-kernel - Re: [PATCHSET x86/mm] memblock, x86: Allow node info in memblock and remove x86 specific memblock code

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:	Wed, 13 Jul 2011 12:06:22 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	mingo@...hat.com, hpa@...or.com, tglx@...utronix.de,
	benh@...nel.crashing.org, davem@...emloft.net,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	x86@...nel.org
Subject: Re: [PATCHSET x86/mm] memblock, x86: Allow node info in memblock and
 remove x86 specific memblock code

On Wed, Jul 13, 2011 at 2:11 AM, Tejun Heo <tj@...nel.org> wrote:
>> looks it comes with some mismatch section warning...
>>
>> WARNING: vmlinux.o(.text+0x120ba5): Section mismatch in reference from
>> the function memblock_set_node() to the variable .init.data:memblock
>> The function memblock_set_node() references
>> the variable __initdata memblock.
>> This is often because memblock_set_node lacks a __initdata
>> annotation or the annotation of memblock is wrong.
>
> Oh, the __memblock_init thing.  Can you please attach .config you
> used?

please check attached config.

Yinghai

Download attachment "config.full.999999" of type "application/octet-stream" (86958 bytes)