linux-kernel - linux-next: build failure after merge of the final tree (akpm tree related)

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:	Mon, 21 Jan 2013 17:08:04 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tang Chen <tangchen@...fujitsu.com>
Subject: linux-next: build failure after merge of the final tree (akpm tree
 related)

Hi all,

After merging the final tree, today's linux-next build (arm defconfig)
failed like this:

mm/memblock.c: In function 'memblock_find_in_range_node':
mm/memblock.c:104:2: error: invalid use of undefined type 'struct movablecore_map'
mm/memblock.c:123:4: error: invalid use of undefined type 'struct movablecore_map'
mm/memblock.c:130:7: error: invalid use of undefined type 'struct movablecore_map'
mm/memblock.c:131:4: error: invalid use of undefined type 'struct movablecore_map'

Caused by commit "page_alloc: bootmem limit with movablecore_map" from
the akpm tree.  The definition of struct movablecore_map is protected by
CONFIG_HAVE_MEMBLOCK_NODE_MAP but its use is not.

I have reverted that commit for today.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped