Skip to contentSkip to conversation

x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

PATCH Superseded Pingfan Liu 2 participants 3 messages Jan 14, 2019 – Jan 15, 2019

Subsystems (3)

v6 of 7 Superseded Latest is v7 →

lore
Share & tools
lore
#0 lore raw

PATCH v6 1/1 x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

People reported a bug on a high end server with many pcie devices, where kernel bootup with crashkernel=384M, and kaslr is enabled. Even though we still see much memory under 896 MB, the finding still failed intermittently. Because currently we can only find region under 896 MB, if w/0 ',high' specified. Then KASLR breaks 896 MB into several parts randomly, and crashkernel reservation need be aligned to 128 MB, that's why failure is found. It raises confusion to the end user that sometimes crashkernel=X works while sometimes fails.
If want to make it succeed, customer can change kernel option to "crashkernel=384M, high". Just this give "crashkernel=xx@yy" a very limited space to behave even though its grammer looks more generic. And we can't answer questions raised from customer that confidently:
1) why it doesn't succeed to reserve 896 MB;
2) what's wrong with memory region under 4G;
3) why I have to add ',high', I only require 384 MB, not 3840 MB. This patch tries to get memory region from 896 MB firstly, then [896MB,4G], finally above 4G.
Dave Young sent the original post, and I just re-post it with commit log improvement as his requirement.
http://lists.infradead.org/pipermail/kexec/2017-October/019571.html
There was an old discussion below (previously posted by Chao Wang):
https://lkml.org/lkml/2013/10/15/601

---
v5 -> v6
discard bottom-up allocation, just repost dyoung's original patch with commit log improved

---
 arch/x86/kernel/setup.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
arch/x86/kernel/setup.c +16 -0
index 3d872a5..fa62c81 100644
@@ -551,6 +551,22 @@ static void __init reserve_crashkernel(void)
 						    high ? CRASH_ADDR_HIGH_MAX
 							 : CRASH_ADDR_LOW_MAX,
 						    crash_size, CRASH_ALIGN);
+#ifdef CONFIG_X86_64
+		/*
+		 * crashkernel=X reserve below 896M fails? Try below 4G
+		 */
+		if (!high && !crash_base)
+			crash_base = memblock_find_in_range(CRASH_ALIGN,
+						(1ULL << 32),
+						crash_size, CRASH_ALIGN);
+		/*
+		 * crashkernel=X reserve below 4G fails? Try MAXMEM
+		 */
+		if (!high && !crash_base)
+			crash_base = memblock_find_in_range(CRASH_ALIGN,
+						CRASH_ADDR_HIGH_MAX,
+						crash_size, CRASH_ALIGN);
+#endif
 		if (!crash_base) {
 			pr_info("crashkernel reservation failed - No suitable area found.\n");
 			return;
Signature · 1 line
2.7.4
#1 lore raw

Hi,

Just fix a few of the commit log comments...

Quoted 5 lines · Pingfan Liu

People reported a bug on a high end server with many pcie devices, where kernel bootup with crashkernel=384M, and kaslr is enabled. Even though we still see much memory under 896 MB, the finding still failed intermittently. Because currently we can only find region under 896 MB, if w/0 ',high' specified. Then KASLR breaks 896 MB into several parts

if w/o
or preferably:
if without

Quoted 5 lines

randomly, and crashkernel reservation need be aligned to 128 MB, that's why failure is found. It raises confusion to the end user that sometimes crashkernel=X works while sometimes fails.
If want to make it succeed, customer can change kernel option to "crashkernel=384M, high". Just this give "crashkernel=xx@yy" a very

no space? just
"crashkernel=384M,high"

Quoted 1 line

limited space to behave even though its grammer looks more generic.

grammar

Quoted 44 lines

And we can't answer questions raised from customer that confidently:
1) why it doesn't succeed to reserve 896 MB;
2) what's wrong with memory region under 4G;
3) why I have to add ',high', I only require 384 MB, not 3840 MB. This patch tries to get memory region from 896 MB firstly, then [896MB,4G], finally above 4G.
Dave Young sent the original post, and I just re-post it with commit log improvement as his requirement.
http://lists.infradead.org/pipermail/kexec/2017-October/019571.html
There was an old discussion below (previously posted by Chao Wang):
https://lkml.org/lkml/2013/10/15/601

---
v5 -> v6
discard bottom-up allocation, just repost dyoung's original patch with commit log improved

---
 arch/x86/kernel/setup.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
arch/x86/kernel/setup.c +9 -0
index 3d872a5..fa62c81 100644
@@ -551,6 +551,22 @@ static void __init reserve_crashkernel(void)
 						    high ? CRASH_ADDR_HIGH_MAX
 							 : CRASH_ADDR_LOW_MAX,
 						    crash_size, CRASH_ALIGN);
+#ifdef CONFIG_X86_64
+		/*
+		 * crashkernel=X reserve below 896M fails? Try below 4G
+		 */
+		if (!high && !crash_base)
+			crash_base = memblock_find_in_range(CRASH_ALIGN,
+						(1ULL << 32),
+						crash_size, CRASH_ALIGN);
+		/*

arch/x86/kernel/setup.c static void __init reserve_crashkernel(void) · line 572

Quoted 10 lines
arch/x86/kernel/setup.c +7 -0
+		 * crashkernel=X reserve below 4G fails? Try MAXMEM
+		 */
+		if (!high && !crash_base)
+			crash_base = memblock_find_in_range(CRASH_ALIGN,
+						CRASH_ADDR_HIGH_MAX,
+						crash_size, CRASH_ALIGN);
+#endif
 		if (!crash_base) {
 			pr_info("crashkernel reservation failed - No suitable area found.\n");
 			return;

ciao.

Signature · 6 lines
~Randy

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
#2 lore raw
Quoted 22 lines · Randy Dunlap

Hi,

Just fix a few of the commit log comments...

Quoted 5 lines · Pingfan Liu

People reported a bug on a high end server with many pcie devices, where kernel bootup with crashkernel=384M, and kaslr is enabled. Even though we still see much memory under 896 MB, the finding still failed intermittently. Because currently we can only find region under 896 MB, if w/0 ',high' specified. Then KASLR breaks 896 MB into several parts

if w/o
or preferably:
if without

Quoted 5 lines

randomly, and crashkernel reservation need be aligned to 128 MB, that's why failure is found. It raises confusion to the end user that sometimes crashkernel=X works while sometimes fails.
If want to make it succeed, customer can change kernel option to "crashkernel=384M, high". Just this give "crashkernel=xx@yy" a very

Quoted 7 lines

no space? just
"crashkernel=384M,high"

Quoted 1 line

limited space to behave even though its grammer looks more generic.

grammar

Thanks for your review, will cc you in next version.

Regards,
Pingfan

Quoted 58 lines
Quoted 44 lines

And we can't answer questions raised from customer that confidently:
1) why it doesn't succeed to reserve 896 MB;
2) what's wrong with memory region under 4G;
3) why I have to add ',high', I only require 384 MB, not 3840 MB. This patch tries to get memory region from 896 MB firstly, then [896MB,4G], finally above 4G.
Dave Young sent the original post, and I just re-post it with commit log improvement as his requirement.
http://lists.infradead.org/pipermail/kexec/2017-October/019571.html
There was an old discussion below (previously posted by Chao Wang):
https://lkml.org/lkml/2013/10/15/601

---
v5 -> v6
discard bottom-up allocation, just repost dyoung's original patch with commit log improved

---
 arch/x86/kernel/setup.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
arch/x86/kernel/setup.c +9 -0
index 3d872a5..fa62c81 100644
@@ -551,6 +551,22 @@ static void __init reserve_crashkernel(void)
                                                  high ? CRASH_ADDR_HIGH_MAX
                                                       : CRASH_ADDR_LOW_MAX,
                                                  crash_size, CRASH_ALIGN);
+#ifdef CONFIG_X86_64
+             /*
+              * crashkernel=X reserve below 896M fails? Try below 4G
+              */
+             if (!high && !crash_base)
+                     crash_base = memblock_find_in_range(CRASH_ALIGN,
+                                             (1ULL << 32),
+                                             crash_size, CRASH_ALIGN);
+             /*

arch/x86/kernel/setup.c static void __init reserve_crashkernel(void) · line 572

Quoted 10 lines
arch/x86/kernel/setup.c +7 -0
+              * crashkernel=X reserve below 4G fails? Try MAXMEM
+              */
+             if (!high && !crash_base)
+                     crash_base = memblock_find_in_range(CRASH_ALIGN,
+                                             CRASH_ADDR_HIGH_MAX,
+                                             crash_size, CRASH_ALIGN);
+#endif
              if (!crash_base) {
                      pr_info("crashkernel reservation failed - No suitable area found.\n");
                      return;

ciao.
--
~Randy