path: root/kernel/crash_dump.c
diff options
authorKairui Song <kasong@redhat.com>2020-03-31 02:15:44 +0800
committerBorislav Petkov <bp@suse.de>2020-04-15 11:21:54 +0200
commit4c5b566c2193e2af82c891daa5303c8899e61044 (patch)
tree7a9f80ce06ab29ce6ed704f4112106b378f143b4 /kernel/crash_dump.c
parent2fa9a3cf3055db07a4835eb7bd48c648cb17ac26 (diff)
crash_dump: Remove no longer used saved_max_pfn
saved_max_pfn was originally introduced in commit 92aa63a5a1bf ("[PATCH] kdump: Retrieve saved max pfn") It used to make sure that the user does not try to read the physical memory beyond saved_max_pfn. But since commit 921d58c0e699 ("vmcore: remove saved_max_pfn check") it's no longer used for the check. This variable doesn't have any users anymore so just remove it. [ bp: Drop the Calgary IOMMU reference from the commit message. ] Signed-off-by: Kairui Song <kasong@redhat.com> Signed-off-by: Borislav Petkov <bp@suse.de> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com> Link: https://lkml.kernel.org/r/20200330181544.1595733-1-kasong@redhat.com
Diffstat (limited to 'kernel/crash_dump.c')
1 files changed, 0 insertions, 6 deletions
diff --git a/kernel/crash_dump.c b/kernel/crash_dump.c
index 9c23ae074b40..92da32275af5 100644
--- a/kernel/crash_dump.c
+++ b/kernel/crash_dump.c
@@ -6,12 +6,6 @@
#include <linux/export.h>
- * If we have booted due to a crash, max_pfn will be a very low value. We need
- * to know the amount of memory that the previous kernel used.
- */
-unsigned long saved_max_pfn;
* stores the physical address of elf header of crash image
* Note: elfcorehdr_addr is not just limited to vmcore. It is also used by

Privacy Policy