mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-13 23:47:04 +07:00
85a0ee342e
The usage of elfcorehdr_addr has changed recently such that being set to ELFCORE_ADDR_MAX is used by is_kdump_kernel() to indicate if the code is executing in a kernel executed as a crash kernel. However, arch/ia64/kernel/setup.c:reserve_elfcorehdr will rest elfcorehdr_addr to ELFCORE_ADDR_MAX on error, which means any subsequent calls to is_kdump_kernel() will return 0, even though they should return 1. Ok, at this point in time there are no subsequent calls, but I think its fair to say that there is ample scope for error or at the very least confusion. This patch add an extra state, ELFCORE_ADDR_ERR, which indicates that elfcorehdr_addr was passed on the command line, and thus execution is taking place in a crashdump kernel, but vmcore can't be used for some reason. This is tested for using is_vmcore_usable() and set using vmcore_unusable(). A subsequent patch makes use of this new code. To summarise, the states that elfcorehdr_addr can now be in are as follows: ELFCORE_ADDR_MAX: not a crashdump kernel ELFCORE_ADDR_ERR: crashdump kernel but vmcore is unusable any other value: crash dump kernel and vmcore is usable Signed-off-by: Simon Horman <horms@verge.net.au> Cc: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
71 lines
2.1 KiB
C
71 lines
2.1 KiB
C
#ifndef LINUX_CRASH_DUMP_H
|
|
#define LINUX_CRASH_DUMP_H
|
|
|
|
#ifdef CONFIG_CRASH_DUMP
|
|
#include <linux/kexec.h>
|
|
#include <linux/smp_lock.h>
|
|
#include <linux/device.h>
|
|
#include <linux/proc_fs.h>
|
|
|
|
#define ELFCORE_ADDR_MAX (-1ULL)
|
|
#define ELFCORE_ADDR_ERR (-2ULL)
|
|
|
|
extern unsigned long long elfcorehdr_addr;
|
|
|
|
extern ssize_t copy_oldmem_page(unsigned long, char *, size_t,
|
|
unsigned long, int);
|
|
extern const struct file_operations proc_vmcore_operations;
|
|
extern struct proc_dir_entry *proc_vmcore;
|
|
|
|
/* Architecture code defines this if there are other possible ELF
|
|
* machine types, e.g. on bi-arch capable hardware. */
|
|
#ifndef vmcore_elf_check_arch_cross
|
|
#define vmcore_elf_check_arch_cross(x) 0
|
|
#endif
|
|
|
|
#define vmcore_elf_check_arch(x) (elf_check_arch(x) || vmcore_elf_check_arch_cross(x))
|
|
|
|
/*
|
|
* is_kdump_kernel() checks whether this kernel is booting after a panic of
|
|
* previous kernel or not. This is determined by checking if previous kernel
|
|
* has passed the elf core header address on command line.
|
|
*
|
|
* This is not just a test if CONFIG_CRASH_DUMP is enabled or not. It will
|
|
* return 1 if CONFIG_CRASH_DUMP=y and if kernel is booting after a panic of
|
|
* previous kernel.
|
|
*/
|
|
|
|
static inline int is_kdump_kernel(void)
|
|
{
|
|
return (elfcorehdr_addr != ELFCORE_ADDR_MAX) ? 1 : 0;
|
|
}
|
|
|
|
/* is_vmcore_usable() checks if the kernel is booting after a panic and
|
|
* the vmcore region is usable.
|
|
*
|
|
* This makes use of the fact that due to alignment -2ULL is not
|
|
* a valid pointer, much in the vain of IS_ERR(), except
|
|
* dealing directly with an unsigned long long rather than a pointer.
|
|
*/
|
|
|
|
static inline int is_vmcore_usable(void)
|
|
{
|
|
return is_kdump_kernel() && elfcorehdr_addr != ELFCORE_ADDR_ERR ? 1 : 0;
|
|
}
|
|
|
|
/* vmcore_unusable() marks the vmcore as unusable,
|
|
* without disturbing the logic of is_kdump_kernel()
|
|
*/
|
|
|
|
static inline void vmcore_unusable(void)
|
|
{
|
|
if (is_kdump_kernel())
|
|
elfcorehdr_addr = ELFCORE_ADDR_ERR;
|
|
}
|
|
#else /* !CONFIG_CRASH_DUMP */
|
|
static inline int is_kdump_kernel(void) { return 0; }
|
|
#endif /* CONFIG_CRASH_DUMP */
|
|
|
|
extern unsigned long saved_max_pfn;
|
|
#endif /* LINUX_CRASHDUMP_H */
|