diff options
| author | Kairui Song <kasong@redhat.com> | 2020-03-31 02:15:44 +0800 |
|---|---|---|
| committer | Borislav Petkov <bp@suse.de> | 2020-04-15 11:21:54 +0200 |
| commit | 4c5b566c2193e2af82c891daa5303c8899e61044 (patch) | |
| tree | 7a9f80ce06ab29ce6ed704f4112106b378f143b4 /include/linux/crash_dump.h | |
| parent | 2fa9a3cf3055db07a4835eb7bd48c648cb17ac26 (diff) | |
| download | lwn-4c5b566c2193e2af82c891daa5303c8899e61044.tar.gz lwn-4c5b566c2193e2af82c891daa5303c8899e61044.zip | |
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 'include/linux/crash_dump.h')
| -rw-r--r-- | include/linux/crash_dump.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/include/linux/crash_dump.h b/include/linux/crash_dump.h index 4664fc1871de..bc156285d097 100644 --- a/include/linux/crash_dump.h +++ b/include/linux/crash_dump.h @@ -97,8 +97,6 @@ extern void unregister_oldmem_pfn_is_ram(void); static inline bool is_kdump_kernel(void) { return 0; } #endif /* CONFIG_CRASH_DUMP */ -extern unsigned long saved_max_pfn; - /* Device Dump information to be filled by drivers */ struct vmcoredd_data { char dump_name[VMCOREDD_MAX_NAME_BYTES]; /* Unique name of the dump */ |