| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 7 Jan 2014 16:16:12 +0100 From: Philipp Hachtmann <phacht@...ux.vnet.ibm.com> To: akpm@...ux-foundation.org, jiang.liu@...wei.com Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, iamjoonsoo.kim@....com, hannes@...xchg.org, tangchen@...fujitsu.com, tj@...nel.org, toshi.kani@...com, Philipp Hachtmann <phacht@...ux.vnet.ibm.com> Subject: [PATCH 0/2] Small fixes to memblock and nobootmem 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists