lk/linux-kernel-test
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[PATCH] x86-64: setup saved_max_pfn correctly (kdump)

Browse Source 
x86_64: setup saved_max_pfn correctly

2.6.19-rc4 has broken CONFIG_CRASH_DUMP support on x86_64. It is impossible
to read out the kernel contents from /proc/vmcore because saved_max_pfn is set
to zero instead of the max_pfn value before the user map is setup.

This happens because saved_max_pfn is initialized at parse_early_param() time,
and at this time no active regions have been registered. save_max_pfn is setup
from e820_end_of_ram(), more exact find_max_pfn_with_active_regions() which
returns 0 because no regions exist.

This patch fixes this by registering before and removing after the call
to e820_end_of_ram().

Signed-off-by: Magnus Damm <magnus@valinux.co.jp>
Signed-off-by: Andi Kleen <ak@suse.de>
This commit is contained in:
Magnus Damm
2006-11-14 16:57:46 +01:00
committed by Andi Kleen
parent 5e58a02a8f
commit 15803a4328
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
arch/x86_64/kernel/e820.c
View File

@@ -594,7 +594,9 @@ static int __init parse_memmap_opt(char *p)
* size before original memory map is * size before original memory map is
* reset. * reset.
*/ */
e820_register_active_regions(0, 0, -1UL);
saved_max_pfn = e820_end_of_ram(); saved_max_pfn = e820_end_of_ram();
remove_all_active_ranges();
#endif #endif
end_pfn_map = 0; end_pfn_map = 0;
e820.nr_map = 0; e820.nr_map = 0;