Blame SOURCES/kexec-tools-2.0.14-Only-print-debug-message-when-failed-to-serach-for-k.patch

766e0d
From f85183096d31d865c97565614535d84943b12908 Mon Sep 17 00:00:00 2001
766e0d
Message-Id: <f85183096d31d865c97565614535d84943b12908.1489676829.git.panand@redhat.com>
766e0d
From: Baoquan He <bhe@redhat.com>
766e0d
Date: Fri, 3 Mar 2017 11:52:15 +0800
766e0d
Subject: [PATCH 01/10] Only print debug message when failed to serach for
766e0d
 kernel symbol from /proc/kallsyms
766e0d
766e0d
Kernel symbol page_offset_base could be unavailable when mm KASLR code is
766e0d
not compiled in kernel. It's inappropriate to print out error message
766e0d
when failed to search for page_offset_base from /proc/kallsyms. Seems now
766e0d
there is not a way to find out if mm KASLR is compiled in or not. An
766e0d
alternative approach is only printing out debug message in get_kernel_sym
766e0d
if failed to search a expected kernel symbol.
766e0d
766e0d
Do it in this patch, a simple fix.
766e0d
766e0d
Signed-off-by: Baoquan He <bhe@redhat.com>
766e0d
Reviewed-by: Pratyush Anand <panand@redhat.com>
766e0d
Acked-by: Dave Young <dyoung@redhat.com>
766e0d
Signed-off-by: Simon Horman <horms@verge.net.au>
766e0d
---
766e0d
 kexec/arch/i386/crashdump-x86.c | 2 +-
766e0d
 1 file changed, 1 insertion(+), 1 deletion(-)
766e0d
766e0d
diff --git a/kexec/arch/i386/crashdump-x86.c b/kexec/arch/i386/crashdump-x86.c
766e0d
index 88aeee33572b..c4cf2013a001 100644
766e0d
--- a/kexec/arch/i386/crashdump-x86.c
766e0d
+++ b/kexec/arch/i386/crashdump-x86.c
766e0d
@@ -127,7 +127,7 @@ static unsigned long long get_kernel_sym(const char *symbol)
766e0d
 		}
766e0d
 	}
766e0d
 
766e0d
-	fprintf(stderr, "Cannot get kernel %s symbol address\n", symbol);
766e0d
+	dbgprintf("Cannot get kernel %s symbol address\n", symbol);
766e0d
 	return 0;
766e0d
 }
766e0d
 
766e0d
-- 
766e0d
2.9.3
766e0d