Register vmcoreinfo information into kmemdump. Because the size of the info is computed after all entries are being added, there is no point in registering the whole page, rather, call the kmemdump registration once everything is in place with the right size. A second reason is that the vmcoreinfo is added as a region inside the ELF coreimage note, there is no point in having blank space at the end.
Signed-off-by: Eugen Hristev <[email protected]> --- kernel/vmcore_info.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/vmcore_info.c b/kernel/vmcore_info.c index e066d31d08f8..d808c5e67f35 100644 --- a/kernel/vmcore_info.c +++ b/kernel/vmcore_info.c @@ -14,6 +14,7 @@ #include <linux/cpuhotplug.h> #include <linux/memblock.h> #include <linux/kmemleak.h> +#include <linux/kmemdump.h> #include <asm/page.h> #include <asm/sections.h> @@ -227,6 +228,8 @@ static int __init crash_save_vmcoreinfo_init(void) arch_crash_save_vmcoreinfo(); update_vmcoreinfo_note(); + kmemdump_register_id(KMEMDUMP_ID_COREIMAGE_VMCOREINFO, + (void *)vmcoreinfo_data, vmcoreinfo_size); return 0; } -- 2.43.0
