linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
@ 2015-09-22 11:48 Baoquan He
  2015-09-22 13:50 ` Baoquan He
  2015-09-22 19:54 ` Andrew Morton
  0 siblings, 2 replies; 6+ messages in thread
From: Baoquan He @ 2015-09-22 11:48 UTC (permalink / raw)
  To: akpm, yinghai, dyoung, jroedel
  Cc: tglx, mingo, hpa, bp, linux-kernel, Baoquan He

People reported that when allocating crashkernel memory using
",high" and ",low" syntax, there were cases where the reservation
of the "high" portion succeeds, but the reservation of the "low"
portion fails. Then kexec can load kdump kernel successfully, but
the boot of kdump kernel fails as there's no low memory. This is
because allocation of low memory for kdump kernel can fail on large
systems for reasons. E.g it could be manually specified crashkernel
low memory is too large to find in memblock region.

In this patch add return value for reserve_crashkernel_low. Then
try to reserve crashkernel low memory after crashkernel high memory
has been allocated. If crashkernel low memory reservation failed
free crashkernel high memory and return. User can take measures
when they found kdump kernel cann't be loaded successfully.

Signed-off-by: Baoquan He <bhe@redhat.com>
---
v1->v2:
  Boris commented that error value EINVAL is negative, should
  use "return -EINVAL".

v2->v3:
  Yinghai pointed out that during memblock_reserve, we could double
  the memblock reserve array. New memblock reserve could be overlapped
  with range for crashkernel high. So we have to reserve crashkernel
  high firstly, then free it if crashkernel low memory allocation
  failed.

v3->v4:
  Dave suggested using "return -ENOMEM" when low memory reservation
  failed and printing failure message anyway.

 arch/x86/kernel/setup.c | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index fdb7f2a..e362f92 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -493,7 +493,7 @@ static void __init memblock_x86_reserve_range_setup_data(void)
 # define CRASH_KERNEL_ADDR_HIGH_MAX	MAXMEM
 #endif
 
-static void __init reserve_crashkernel_low(void)
+static int __init reserve_crashkernel_low(void)
 {
 #ifdef CONFIG_X86_64
 	const unsigned long long alignment = 16<<20;	/* 16M */
@@ -522,17 +522,15 @@ static void __init reserve_crashkernel_low(void)
 	} else {
 		/* passed with crashkernel=0,low ? */
 		if (!low_size)
-			return;
+			return 0;
 	}
 
 	low_base = memblock_find_in_range(low_size, (1ULL<<32),
 					low_size, alignment);
 
 	if (!low_base) {
-		if (!auto_set)
-			pr_info("crashkernel low reservation failed - No suitable area found.\n");
-
-		return;
+		pr_info("crashkernel low reservation failed - No suitable area found.\n");
+		return -ENOMEM;
 	}
 
 	memblock_reserve(low_base, low_size);
@@ -544,6 +542,7 @@ static void __init reserve_crashkernel_low(void)
 	crashk_low_res.end   = low_base + low_size - 1;
 	insert_resource(&iomem_resource, &crashk_low_res);
 #endif
+	return 0;
 }
 
 static void __init reserve_crashkernel(void)
@@ -595,6 +594,11 @@ static void __init reserve_crashkernel(void)
 	}
 	memblock_reserve(crash_base, crash_size);
 
+	if (crash_base >= (1ULL<<32) && reserve_crashkernel_low()) {
+		memblock_free(crash_base, crash_size);
+		return;
+	}
+
 	printk(KERN_INFO "Reserving %ldMB of memory at %ldMB "
 			"for crashkernel (System RAM: %ldMB)\n",
 			(unsigned long)(crash_size >> 20),
@@ -604,9 +608,6 @@ static void __init reserve_crashkernel(void)
 	crashk_res.start = crash_base;
 	crashk_res.end   = crash_base + crash_size - 1;
 	insert_resource(&iomem_resource, &crashk_res);
-
-	if (crash_base >= (1ULL<<32))
-		reserve_crashkernel_low();
 }
 #else
 static void __init reserve_crashkernel(void)
-- 
2.1.0


^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
  2015-09-22 11:48 [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed Baoquan He
@ 2015-09-22 13:50 ` Baoquan He
  2015-09-22 19:54 ` Andrew Morton
  1 sibling, 0 replies; 6+ messages in thread
From: Baoquan He @ 2015-09-22 13:50 UTC (permalink / raw)
  To: akpm, yinghai, dyoung, jroedel, jerry_hoemann
  Cc: tglx, mingo, hpa, bp, linux-kernel

Add Jerry to CC list. 

On 09/22/15 at 07:48pm, Baoquan He wrote:
> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
> portion fails. Then kexec can load kdump kernel successfully, but
> the boot of kdump kernel fails as there's no low memory. This is
> because allocation of low memory for kdump kernel can fail on large
> systems for reasons. E.g it could be manually specified crashkernel
> low memory is too large to find in memblock region.
> 
> In this patch add return value for reserve_crashkernel_low. Then
> try to reserve crashkernel low memory after crashkernel high memory
> has been allocated. If crashkernel low memory reservation failed
> free crashkernel high memory and return. User can take measures
> when they found kdump kernel cann't be loaded successfully.
> 
> Signed-off-by: Baoquan He <bhe@redhat.com>
> ---
> v1->v2:
>   Boris commented that error value EINVAL is negative, should
>   use "return -EINVAL".
> 
> v2->v3:
>   Yinghai pointed out that during memblock_reserve, we could double
>   the memblock reserve array. New memblock reserve could be overlapped
>   with range for crashkernel high. So we have to reserve crashkernel
>   high firstly, then free it if crashkernel low memory allocation
>   failed.
> 
> v3->v4:
>   Dave suggested using "return -ENOMEM" when low memory reservation
>   failed and printing failure message anyway.
> 
>  arch/x86/kernel/setup.c | 19 ++++++++++---------
>  1 file changed, 10 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> index fdb7f2a..e362f92 100644
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -493,7 +493,7 @@ static void __init memblock_x86_reserve_range_setup_data(void)
>  # define CRASH_KERNEL_ADDR_HIGH_MAX	MAXMEM
>  #endif
>  
> -static void __init reserve_crashkernel_low(void)
> +static int __init reserve_crashkernel_low(void)
>  {
>  #ifdef CONFIG_X86_64
>  	const unsigned long long alignment = 16<<20;	/* 16M */
> @@ -522,17 +522,15 @@ static void __init reserve_crashkernel_low(void)
>  	} else {
>  		/* passed with crashkernel=0,low ? */
>  		if (!low_size)
> -			return;
> +			return 0;
>  	}
>  
>  	low_base = memblock_find_in_range(low_size, (1ULL<<32),
>  					low_size, alignment);
>  
>  	if (!low_base) {
> -		if (!auto_set)
> -			pr_info("crashkernel low reservation failed - No suitable area found.\n");
> -
> -		return;
> +		pr_info("crashkernel low reservation failed - No suitable area found.\n");
> +		return -ENOMEM;
>  	}
>  
>  	memblock_reserve(low_base, low_size);
> @@ -544,6 +542,7 @@ static void __init reserve_crashkernel_low(void)
>  	crashk_low_res.end   = low_base + low_size - 1;
>  	insert_resource(&iomem_resource, &crashk_low_res);
>  #endif
> +	return 0;
>  }
>  
>  static void __init reserve_crashkernel(void)
> @@ -595,6 +594,11 @@ static void __init reserve_crashkernel(void)
>  	}
>  	memblock_reserve(crash_base, crash_size);
>  
> +	if (crash_base >= (1ULL<<32) && reserve_crashkernel_low()) {
> +		memblock_free(crash_base, crash_size);
> +		return;
> +	}
> +
>  	printk(KERN_INFO "Reserving %ldMB of memory at %ldMB "
>  			"for crashkernel (System RAM: %ldMB)\n",
>  			(unsigned long)(crash_size >> 20),
> @@ -604,9 +608,6 @@ static void __init reserve_crashkernel(void)
>  	crashk_res.start = crash_base;
>  	crashk_res.end   = crash_base + crash_size - 1;
>  	insert_resource(&iomem_resource, &crashk_res);
> -
> -	if (crash_base >= (1ULL<<32))
> -		reserve_crashkernel_low();
>  }
>  #else
>  static void __init reserve_crashkernel(void)
> -- 
> 2.1.0
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
  2015-09-22 11:48 [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed Baoquan He
  2015-09-22 13:50 ` Baoquan He
@ 2015-09-22 19:54 ` Andrew Morton
  2015-09-23  0:02   ` Baoquan He
  1 sibling, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2015-09-22 19:54 UTC (permalink / raw)
  To: Baoquan He; +Cc: yinghai, dyoung, jroedel, tglx, mingo, hpa, bp, linux-kernel

On Tue, 22 Sep 2015 19:48:14 +0800 Baoquan He <bhe@redhat.com> wrote:

> People reported that when allocating crashkernel memory using
> ",high" and ",low" syntax, there were cases where the reservation
> of the "high" portion succeeds, but the reservation of the "low"
> portion fails. Then kexec can load kdump kernel successfully, but
> the boot of kdump kernel fails as there's no low memory. This is
> because allocation of low memory for kdump kernel can fail on large
> systems for reasons. E.g it could be manually specified crashkernel
> low memory is too large to find in memblock region.
> 
> In this patch add return value for reserve_crashkernel_low. Then
> try to reserve crashkernel low memory after crashkernel high memory
> has been allocated. If crashkernel low memory reservation failed
> free crashkernel high memory and return. User can take measures
> when they found kdump kernel cann't be loaded successfully.
>
> ...
>
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@ -493,7 +493,7 @@ static void __init memblock_x86_reserve_range_setup_data(void)
>  # define CRASH_KERNEL_ADDR_HIGH_MAX	MAXMEM
>  #endif
>  
> -static void __init reserve_crashkernel_low(void)
> +static int __init reserve_crashkernel_low(void)
>  {
>  #ifdef CONFIG_X86_64
>  	const unsigned long long alignment = 16<<20;	/* 16M */
> @@ -522,17 +522,15 @@ static void __init reserve_crashkernel_low(void)
>  	} else {
>  		/* passed with crashkernel=0,low ? */
>  		if (!low_size)
> -			return;
> +			return 0;

What's happening here?  It's returning "success" when
parse_crashkernel_low() fails?

>  	}
>  
>  	low_base = memblock_find_in_range(low_size, (1ULL<<32),
>  					low_size, alignment);
>  
>  	if (!low_base) {
> -		if (!auto_set)
> -			pr_info("crashkernel low reservation failed - No suitable area found.\n");
> -
> -		return;
> +		pr_info("crashkernel low reservation failed - No suitable area found.\n");

That's not a terribly useful message.  If kdump is now unavailable and
the operator needs to take some remedial action then we should inform
them of this.

Also, such a message should have higher severity than KERN_INFO?


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
  2015-09-22 19:54 ` Andrew Morton
@ 2015-09-23  0:02   ` Baoquan He
  2015-09-23  0:08     ` Andrew Morton
  0 siblings, 1 reply; 6+ messages in thread
From: Baoquan He @ 2015-09-23  0:02 UTC (permalink / raw)
  To: Andrew Morton
  Cc: yinghai, dyoung, jroedel, tglx, mingo, hpa, bp, linux-kernel

On 09/22/15 at 12:54pm, Andrew Morton wrote:
> > --- a/arch/x86/kernel/setup.c
> > +++ b/arch/x86/kernel/setup.c
> > @@ -493,7 +493,7 @@ static void __init memblock_x86_reserve_range_setup_data(void)
> >  # define CRASH_KERNEL_ADDR_HIGH_MAX	MAXMEM
> >  #endif
> >  
> > -static void __init reserve_crashkernel_low(void)
> > +static int __init reserve_crashkernel_low(void)
> >  {
> >  #ifdef CONFIG_X86_64
> >  	const unsigned long long alignment = 16<<20;	/* 16M */
> > @@ -522,17 +522,15 @@ static void __init reserve_crashkernel_low(void)
> >  	} else {
> >  		/* passed with crashkernel=0,low ? */
> >  		if (!low_size)
> > -			return;
> > +			return 0;
> 
> What's happening here?  It's returning "success" when
> parse_crashkernel_low() fails?

It's the case user specify "crashkernel=0,low" to disable
crashkernel low memory allocation explicitly. So here we parse the
cmdline and get it's in this case, reture 0 directly.

> 
> >  	}
> >  
> >  	low_base = memblock_find_in_range(low_size, (1ULL<<32),
> >  					low_size, alignment);
> >  
> >  	if (!low_base) {
> > -		if (!auto_set)
> > -			pr_info("crashkernel low reservation failed - No suitable area found.\n");
> > -
> > -		return;
> > +		pr_info("crashkernel low reservation failed - No suitable area found.\n");
> 
> That's not a terribly useful message.  If kdump is now unavailable and
> the operator needs to take some remedial action then we should inform
> them of this.
> 
> Also, such a message should have higher severity than KERN_INFO?

Yes, how about KERN_ERR? It's an unexpected result from kdump side
though it doesn't harm the normal kernel.


> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
  2015-09-23  0:02   ` Baoquan He
@ 2015-09-23  0:08     ` Andrew Morton
  2015-09-23  0:20       ` Baoquan He
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2015-09-23  0:08 UTC (permalink / raw)
  To: Baoquan He; +Cc: yinghai, dyoung, jroedel, tglx, mingo, hpa, bp, linux-kernel

On Wed, 23 Sep 2015 08:02:55 +0800 Baoquan He <bhe@redhat.com> wrote:

> > 
> > >  	}
> > >  
> > >  	low_base = memblock_find_in_range(low_size, (1ULL<<32),
> > >  					low_size, alignment);
> > >  
> > >  	if (!low_base) {
> > > -		if (!auto_set)
> > > -			pr_info("crashkernel low reservation failed - No suitable area found.\n");
> > > -
> > > -		return;
> > > +		pr_info("crashkernel low reservation failed - No suitable area found.\n");
> > 
> > That's not a terribly useful message.  If kdump is now unavailable and
> > the operator needs to take some remedial action then we should inform
> > them of this.
> > 
> > Also, such a message should have higher severity than KERN_INFO?
> 
> Yes, how about KERN_ERR? It's an unexpected result from kdump side
> though it doesn't harm the normal kernel.

Sure, KERN_ERR is good.  Along with more useful message text.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed
  2015-09-23  0:08     ` Andrew Morton
@ 2015-09-23  0:20       ` Baoquan He
  0 siblings, 0 replies; 6+ messages in thread
From: Baoquan He @ 2015-09-23  0:20 UTC (permalink / raw)
  To: Andrew Morton
  Cc: yinghai, dyoung, jroedel, tglx, mingo, hpa, bp, linux-kernel

On 09/22/15 at 05:08pm, Andrew Morton wrote:
> On Wed, 23 Sep 2015 08:02:55 +0800 Baoquan He <bhe@redhat.com> wrote:
> 
> > > 
> > > >  	}
> > > >  
> > > >  	low_base = memblock_find_in_range(low_size, (1ULL<<32),
> > > >  					low_size, alignment);
> > > >  
> > > >  	if (!low_base) {
> > > > -		if (!auto_set)
> > > > -			pr_info("crashkernel low reservation failed - No suitable area found.\n");
> > > > -
> > > > -		return;
> > > > +		pr_info("crashkernel low reservation failed - No suitable area found.\n");
> > > 
> > > That's not a terribly useful message.  If kdump is now unavailable and
> > > the operator needs to take some remedial action then we should inform
> > > them of this.
> > > 
> > > Also, such a message should have higher severity than KERN_INFO?
> > 
> > Yes, how about KERN_ERR? It's an unexpected result from kdump side
> > though it doesn't harm the normal kernel.
> 
> Sure, KERN_ERR is good.  Along with more useful message text.

OK, will do. Thanks for your suggestion.



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-09-23  0:20 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-22 11:48 [Patch v4] Do not reserve crashkernel high memory if crashkernel low memory reserving failed Baoquan He
2015-09-22 13:50 ` Baoquan He
2015-09-22 19:54 ` Andrew Morton
2015-09-23  0:02   ` Baoquan He
2015-09-23  0:08     ` Andrew Morton
2015-09-23  0:20       ` Baoquan He

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).