mm: disallow early_pfn_to_nid on configurations which do not implement it
authorMichal Hocko <>
Mon, 10 Jul 2017 22:50:12 +0000 (15:50 -0700)
committerLinus Torvalds <>
Mon, 10 Jul 2017 23:32:33 +0000 (16:32 -0700)
early_pfn_to_nid will return node 0 if both HAVE_ARCH_EARLY_PFN_TO_NID
and HAVE_MEMBLOCK_NODE_MAP are disabled.  It seems we are safe now
because all architectures which support NUMA define one of them (with an
exception of alpha which however has CONFIG_NUMA marked as broken) so
this works as expected.  It can get silently and subtly broken too
easily, though.  Make sure we fail the compilation if NUMA is enabled
and there is no proper implementation for this function.  If that ever
happens we know that either the specific configuration is invalid and
the fix should either disable NUMA or enable one of the above configs.

Signed-off-by: Michal Hocko <>
Acked-by: Vlastimil Babka <>
Cc: Joonsoo Kim <>
Cc: Yang Shi <>
Cc: Mel Gorman <>
Signed-off-by: Andrew Morton <>
Signed-off-by: Linus Torvalds <>

index 16532fa0bb64cd13551df531372a4b9c4244359e..fc14b8b3f6ce8a7cdd2a70ef89906c22d52f3b55 100644 (file)
@@ -1055,6 +1055,7 @@ static inline struct zoneref *first_zones_zonelist(struct zonelist *zonelist,
 static inline unsigned long early_pfn_to_nid(unsigned long pfn)
        return 0;