x86: fix memory setup bug

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Linux Kernel Mailing List
Date: Monday, July 14, 2008 - 4:54 pm

Gitweb:     http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b9d19f...
Commit:     b9d19f4a51447930db002409945ad40a7a373cb0
Parent:     383bc5cecc2ed0b8f44a25488660b03030425ef7
Author:     Yinghai Lu <yhlu.kernel@gmail.com>
AuthorDate: Thu Jun 26 00:44:56 2008 -0700
Committer:  Ingo Molnar <mingo@elte.hu>
CommitDate: Tue Jul 8 13:10:42 2008 +0200

    x86: fix memory setup bug
    
    interesting...
    
    [    0.000000]   mapped low ram: 0 - 20000000
    [    0.000000]   low ram: 00000000 - 1fff0000
    [    0.000000]   bootmap 00002000 - 00006000
    
    max_pfn_mapped > max_low_pfn?
    
    it seems init_memory_mapping reveals an old bug.
    
    please check attached test patch.
    
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/kernel/setup_32.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/setup_32.c b/arch/x86/kernel/setup_32.c
index 4b953dc..392812d 100644
--- a/arch/x86/kernel/setup_32.c
+++ b/arch/x86/kernel/setup_32.c
@@ -427,7 +427,7 @@ void __init setup_arch(char **cmdline_p)
 	find_low_pfn_range();
 
 	/* max_pfn_mapped is updated here */
-	init_memory_mapping(0, (max_low_pfn << PAGE_SHIFT));
+	max_pfn_mapped = init_memory_mapping(0, (max_low_pfn << PAGE_SHIFT));
 
 	reserve_initrd();
 
--
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
x86: fix memory setup bug, Linux Kernel Mailing ..., (Mon Jul 14, 4:54 pm)