From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 08/23] mm/memblock: debug: don't free reserved array if !ARCH_DISCARD_MEMBLOCK
Date: Mon, 14 Oct 2013 10:41:50 -0400 [thread overview]
Message-ID: <525C02AE.8040507@ti.com> (raw)
In-Reply-To: <20131013195111.GB18075@htj.dyndns.org>
On Sunday 13 October 2013 03:51 PM, Tejun Heo wrote:
> On Sat, Oct 12, 2013 at 05:58:51PM -0400, Santosh Shilimkar wrote:
>> From: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Now the Nobootmem allocator will always try to free memory allocated for
>> reserved memory regions (free_low_memory_core_early()) without taking
>> into to account current memblock debugging configuration
>> (CONFIG_ARCH_DISCARD_MEMBLOCK and CONFIG_DEBUG_FS state).
>> As result if:
>> - CONFIG_DEBUG_FS defined
>> - CONFIG_ARCH_DISCARD_MEMBLOCK not defined;
>> - reserved memory regions array have been resized during boot
>>
>> then:
>> - memory allocated for reserved memory regions array will be freed to
>> buddy allocator;
>> - debug_fs entry "sys/kernel/debug/memblock/reserved" will show garbage
>> instead of state of memory reservations. like:
>> 0: 0x98393bc0..0x9a393bbf
>> 1: 0xff120000..0xff11ffff
>> 2: 0x00000000..0xffffffff
>>
>> Hence, do not free memory allocated for reserved memory regions if
>> defined(CONFIG_DEBUG_FS) && !defined(CONFIG_ARCH_DISCARD_MEMBLOCK).
>>
>> Cc: Yinghai Lu <yinghai@kernel.org>
>> Cc: Tejun Heo <tj@kernel.org>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
>> mm/memblock.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/mm/memblock.c b/mm/memblock.c
>> index d903138..1bb2cc0 100644
>> --- a/mm/memblock.c
>> +++ b/mm/memblock.c
>> @@ -169,6 +169,10 @@ phys_addr_t __init_memblock get_allocated_memblock_reserved_regions_info(
>> if (memblock.reserved.regions == memblock_reserved_init_regions)
>> return 0;
>>
>
> Please add comment explaining why the following test exists. It's
> pretty difficult to deduce the reason only from the code.
>
ok.
>> + if (IS_ENABLED(CONFIG_DEBUG_FS) &&
>> + !IS_ENABLED(CONFIG_ARCH_DISCARD_MEMBLOCK))
>> + return 0;
>> +
>
> Also, as this is another fix patch, can you please move this to the
> head of the series?
>
Sure
next prev parent reply other threads:[~2013-10-14 14:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 21:58 [RFC 00/23] mm: Use memblock interface instead of bootmem Santosh Shilimkar
2013-10-12 21:59 ` [RFC 20/23] mm/firmware: Use memblock apis for early memory allocations Santosh Shilimkar
[not found] ` <1381615146-20342-7-git-send-email-santosh.shilimkar@ti.com>
2013-10-13 17:56 ` [RFC 06/23] mm/memblock: Add memblock early memory allocation apis Tejun Heo
2013-10-13 18:00 ` Russell King - ARM Linux
2013-10-13 18:42 ` Tejun Heo
2013-10-14 13:48 ` Santosh Shilimkar
2013-10-14 14:39 ` Santosh Shilimkar
2013-10-14 14:58 ` Tejun Heo
2013-10-14 15:03 ` Santosh Shilimkar
[not found] ` <1381615146-20342-8-git-send-email-santosh.shilimkar@ti.com>
2013-10-13 18:02 ` [RFC 07/23] mm/memblock: debug: correct displaying of upper memory boundary Tejun Heo
2013-10-14 14:41 ` Santosh Shilimkar
[not found] ` <1381615146-20342-9-git-send-email-santosh.shilimkar@ti.com>
2013-10-13 19:51 ` [RFC 08/23] mm/memblock: debug: don't free reserved array if !ARCH_DISCARD_MEMBLOCK Tejun Heo
2013-10-14 14:41 ` Santosh Shilimkar [this message]
[not found] ` <1381615146-20342-10-git-send-email-santosh.shilimkar@ti.com>
2013-10-13 19:54 ` [RFC 09/23] mm/init: Use memblock apis for early memory allocations Tejun Heo
2013-10-14 14:43 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525C02AE.8040507@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).