fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp. CONFIG_HAVE_MEMBLOCK_NODE_MAP. early_pfn_to_nid is returning zero with !defined(CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID) && !defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP) I am not sure how widely is this used but such a code is tricky. I see how catching early allocations during defered initialization might be useful but a subtly broken code sounds like a problem to me. So is fe53ca54270a worth this or we should revert it? -- Michal Hocko SUSE Labs
- "mm: use early_pfn_to_nid in page_ext_init" brok... Michal Hocko
- Re: "mm: use early_pfn_to_nid in page_ext_init&q... Michal Hocko
- Re: "mm: use early_pfn_to_nid in page_ext_in... Michal Hocko
- Re: "mm: use early_pfn_to_nid in page_ex... Joonsoo Kim
- Re: "mm: use early_pfn_to_nid in pag... Michal Hocko
- Re: "mm: use early_pfn_to_nid in page_ext_init&q... Vlastimil Babka
- Re: "mm: use early_pfn_to_nid in page_ext_in... Vlastimil Babka
- Re: "mm: use early_pfn_to_nid in page_ex... Joonsoo Kim
- Re: "mm: use early_pfn_to_nid in pag... Vlastimil Babka
- Re: "mm: use early_pfn_to_nid i... Michal Hocko
- Re: "mm: use early_pfn_to_nid in page_ext_in... Joonsoo Kim