From: Philipp Hachtmann <phacht@linux.vnet.ibm.com>
To: akpm@linux-foundation.org, jiang.liu@huawei.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
iamjoonsoo.kim@lge.com, hannes@cmpxchg.org,
tangchen@cn.fujitsu.com, tj@kernel.org, toshi.kani@hp.com,
Philipp Hachtmann <phacht@linux.vnet.ibm.com>
Subject: [PATCH 0/2] Small fixes to memblock and nobootmem
Date: Tue, 7 Jan 2014 16:16:12 +0100 [thread overview]
Message-ID: <1389107774-54978-1-git-send-email-phacht@linux.vnet.ibm.com> (raw)
While working on the conversion of the s390 port to use memblock and
nobootmem instead of bootmem I discovered two small bugs:
alloc_memory_core_early() in mm/nobootmem.c called memblock_reserve()
without forwarding the return value of memblock_reserve().
free_low_memory_core() (used by free_all_bootmem) in mm/nobootmem.c
already took care of releasing the memblock.reserved array in case
it has been allocated using memblock itself. This behaviour was
missing for memblock.memory.
Cases where memblock.memory grows bigger than the initial 128 entries
have been seen. So this should be supported as well.
Philipp Hachtmann (2):
mm, nobootmem: Add return value check in __alloc_memory_core_early()
mm: free memblock.memory in free_all_bootmem
include/linux/memblock.h | 1 +
mm/memblock.c | 12 ++++++++++++
mm/nobootmem.c | 11 +++++++++--
3 files changed, 22 insertions(+), 2 deletions(-)
--
1.8.4.5
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-01-07 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 15:16 Philipp Hachtmann [this message]
2014-01-07 15:16 ` [PATCH 1/2] mm, nobootmem: Add return value check in __alloc_memory_core_early() Philipp Hachtmann
2014-01-07 15:19 ` Tejun Heo
2014-01-07 15:16 ` [PATCH 2/2] mm: free memblock.memory in free_all_bootmem Philipp Hachtmann
2014-01-07 15:23 ` Tejun Heo
2014-01-08 4:08 ` Jianguo Wu
2014-01-08 13:42 ` Philipp Hachtmann
2014-01-08 23:30 ` Yinghai Lu
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=1389107774-54978-1-git-send-email-phacht@linux.vnet.ibm.com \
--to=phacht@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tangchen@cn.fujitsu.com \
--cc=tj@kernel.org \
--cc=toshi.kani@hp.com \
/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