KASLR does not work in kdump kernel because it's too early that mem=exactmap has not been parsed.
Since KASLR does not make much sense for kdump kernel thus let's disable it for kdump kernel. To check if it is a kdump kernel I just check the cmdline param elfcorehdr just like is_kdump_kernel. Signed-off-by: Dave Young <[email protected]> --- linux-2.6/arch/x86/boot/compressed/aslr.c | 5 +++++ 1 file changed, 5 insertions(+) Index: dyoung/git/linux-2.6/arch/x86/boot/compressed/aslr.c =================================================================== --- linux-2.6/arch/x86/boot/compressed/aslr.c +++ linux-2.6/arch/x86/boot/compressed/aslr.c @@ -293,6 +293,11 @@ unsigned char *choose_kernel_location(un goto out; } + if (cmdline_find_option("elfcorehdr", NULL, 0) != -1) { + debug_putstr("KASLR disabled...\n"); + goto out; + } + /* Record the various known unsafe memory ranges. */ mem_avoid_init((unsigned long)input, input_size, (unsigned long)output, output_size); -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
