All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix allocation done in get_free_all_memory_range()
Date: Fri, 26 Mar 2010 13:33:13 -0700	[thread overview]
Message-ID: <4BAD1A09.7030702@kernel.org> (raw)
In-Reply-To: <4BACF1CB020000780003737A@vpn.id2.novell.com>

On 03/26/2010 09:41 AM, Jan Beulich wrote:
> Even when get_max_mapped() returns a value beyond the DMA32 range,
> this can't be taken to mean an alocation from that range will succeed.
> Hence, the code should still fall back to an allocation starting at
> the bottom of memory if the first one failed.
> 
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> 
> ---
>  kernel/early_res.c |   10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> --- linux-2.6.34-rc2/kernel/early_res.c	2010-03-25 15:23:45.000000000 +0100
> +++ 2.6.34-rc2-get_free_all_memory_range-retry-alloc/kernel/early_res.c	2010-03-26 14:49:41.000000000 +0100
> @@ -387,9 +387,7 @@ static void __init subtract_early_res(st
>  int __init get_free_all_memory_range(struct range **rangep, int nodeid)
>  {
>  	int i, count;
> -	u64 start = 0, end;
> -	u64 size;
> -	u64 mem;
> +	u64 end, size, mem = -1ULL;
>  	struct range *range;
>  	int nr_range;
>  
> @@ -403,9 +401,11 @@ int __init get_free_all_memory_range(str
>  	end = get_max_mapped();
>  #ifdef MAX_DMA32_PFN
>  	if (end > (MAX_DMA32_PFN << PAGE_SHIFT))
> -		start = MAX_DMA32_PFN << PAGE_SHIFT;
> +		mem = find_fw_memmap_area(MAX_DMA32_PFN << PAGE_SHIFT, end,
> +					  size, sizeof(struct range));
>  #endif
> -	mem = find_fw_memmap_area(start, end, size, sizeof(struct range));
> +	if (mem == -1ULL)
> +		mem = find_fw_memmap_area(0, end, size, sizeof(struct range));
>  	if (mem == -1ULL)
>  		panic("can not find more space for range free");

Acked-by: Yinghai Lu <yinghai@kernel.org>

Thanks for catching it.

Yinghai

      reply	other threads:[~2010-03-26 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 16:41 [PATCH] fix allocation done in get_free_all_memory_range() Jan Beulich
2010-03-26 20:33 ` Yinghai Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BAD1A09.7030702@kernel.org \
    --to=yinghai@kernel.org \
    --cc=JBeulich@novell.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.