[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b52f21d3-3abe-69e2-ae17-6e9f892b49d4@oracle.com>
Date: Mon, 14 Aug 2017 09:32:01 -0400
From: Pasha Tatashin <pasha.tatashin@...cle.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
x86@...nel.org, kasan-dev@...glegroups.com, borntraeger@...ibm.com,
heiko.carstens@...ibm.com, davem@...emloft.net,
willy@...radead.org, ard.biesheuvel@...aro.org,
will.deacon@....com, catalin.marinas@....com, sam@...nborg.org
Subject: Re: [v6 02/15] x86/mm: setting fields in deferred pages
On 08/14/2017 07:43 AM, Michal Hocko wrote:
>> register_page_bootmem_info
>> register_page_bootmem_info_node
>> get_page_bootmem
>> .. setting fields here ..
>> such as: page->freelist = (void *)type;
>>
>> free_all_bootmem()
>> free_low_memory_core_early()
>> for_each_reserved_mem_region()
>> reserve_bootmem_region()
>> init_reserved_page() <- Only if this is deferred reserved page
>> __init_single_pfn()
>> __init_single_page()
>> memset(0) <-- Loose the set fields here!
> OK, I have missed that part. Please make it explicit in the changelog.
> It is quite easy to get lost in the deep call chains.
Ok, will update comment.
Powered by blists - more mailing lists