[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250724135512.518487-22-eugen.hristev@linaro.org>
Date: Thu, 24 Jul 2025 16:55:04 +0300
From: Eugen Hristev <eugen.hristev@...aro.org>
To: linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org,
linux-arch@...r.kernel.org,
linux-mm@...ck.org,
tglx@...utronix.de,
andersson@...nel.org,
pmladek@...e.com
Cc: linux-arm-kernel@...ts.infradead.org,
linux-hardening@...r.kernel.org,
eugen.hristev@...aro.org,
corbet@....net,
mojha@....qualcomm.com,
rostedt@...dmis.org,
jonechou@...gle.com,
tudor.ambarus@...aro.org
Subject: [RFC][PATCH v2 21/29] kernel/configs: Register dynamic information into Kmemdump
Register kernel_config_data information into kmemdump.
Debugging tools look for the start and end markers, so we need to capture
those as well into the region.
Signed-off-by: Eugen Hristev <eugen.hristev@...aro.org>
---
kernel/configs.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/kernel/configs.c b/kernel/configs.c
index a28c79c5f713..ec94b695f234 100644
--- a/kernel/configs.c
+++ b/kernel/configs.c
@@ -15,6 +15,7 @@
#include <linux/seq_file.h>
#include <linux/init.h>
#include <linux/uaccess.h>
+#include <linux/kmemdump.h>
/*
* "IKCFG_ST" and "IKCFG_ED" are used to extract the config data from
@@ -64,6 +65,11 @@ static int __init ikconfig_init(void)
proc_set_size(entry, &kernel_config_data_end - &kernel_config_data);
+ /* Register 8 bytes before and after, to catch the marker too */
+ kmemdump_register_id(KMEMDUMP_ID_COREIMAGE_CONFIG,
+ (void *)&kernel_config_data - 8,
+ &kernel_config_data_end - &kernel_config_data + 16);
+
return 0;
}
--
2.43.0
Powered by blists - more mailing lists