Messages in this thread Patch in this message | | | From | Joonsoo Kim <> | Subject | [PATCH 1/3] mm, nobootmem: fix wrong usage of max_low_pfn | Date | Tue, 19 Mar 2013 14:15:59 +0900 |
| |
max_low_pfn reflect the number of _pages_ in the system, not the maximum PFN. You can easily find that fact in init_bootmem(). So fix it.
Additionally, if 'start_pfn == end_pfn', we don't need to go futher, so change range check.
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
diff --git a/mm/nobootmem.c b/mm/nobootmem.c index 5e07d36..4711e91 100644 --- a/mm/nobootmem.c +++ b/mm/nobootmem.c @@ -110,9 +110,9 @@ static unsigned long __init __free_memory_core(phys_addr_t start, { unsigned long start_pfn = PFN_UP(start); unsigned long end_pfn = min_t(unsigned long, - PFN_DOWN(end), max_low_pfn); + PFN_DOWN(end), min_low_pfn); - if (start_pfn > end_pfn) + if (start_pfn >= end_pfn) return 0; __free_pages_memory(start_pfn, end_pfn); -- 1.7.9.5
| |