Message ID | 20191122015349.DnuP3a202%akpm@linux-foundation.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [1/4] mm/sparse: consistently do not zero memmap | expand |
On Thu, Nov 21, 2019 at 5:53 PM <akpm@linux-foundation.org> wrote: > > AFAICS this difference does not appear to be on purpose. If the code is > supposed to work with non-initialized memory (__init_single_page() takes > care of zeroing the struct pages which are actually used), we should > consistently not zero the memory, to avoid masking bugs. > This does not seem to be an actual fix, and I will not apply it this late in the rc game. Andrew, please stop sending cleanups as "fixes". Linus
--- a/mm/sparse.c~mm-sparse-consistently-do-not-zero-memmap +++ a/mm/sparse.c @@ -458,7 +458,7 @@ struct page __init *__populate_section_m if (map) return map; - map = memblock_alloc_try_nid(size, + map = memblock_alloc_try_nid_raw(size, PAGE_SIZE, addr, MEMBLOCK_ALLOC_ACCESSIBLE, nid); if (!map)