public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: keith mannthey <kmannth@us.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	lhms-devel <lhms-devel@lists.sourceforge.net>,
	"y-goto@jp.fujitsu.com" <y-goto@jp.fujitsu.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] memory hotadd fixes [3/5] find_next_system_ram catch range fix
Date: Thu, 03 Aug 2006 17:08:12 -0700	[thread overview]
Message-ID: <1154650093.5925.42.camel@keithlap> (raw)
In-Reply-To: <20060803123441.92e4ddfb.kamezawa.hiroyu@jp.fujitsu.com>

On Thu, 2006-08-03 at 12:34 +0900, KAMEZAWA Hiroyuki wrote:
>  find_next_system_ram() is used to find available memory resource
> at onlining newly added memory.
> This patch fixes following problem.
> 
> find_next_system_ram() cannot catch this case.
> 
> Resource:      (start)-------------(end)
> Section :                (start)-------------(end)
> 
> 
> Signed-Off-By: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> 
>  kernel/resource.c   |    3 ++-
>  mm/memory_hotplug.c |    2 +-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6.18-rc3/kernel/resource.c
> ===================================================================
> --- linux-2.6.18-rc3.orig/kernel/resource.c	2006-08-01 16:38:45.000000000 +0900
> +++ linux-2.6.18-rc3/kernel/resource.c	2006-08-01 16:38:56.000000000 +0900
> @@ -244,6 +244,7 @@
>  
>  	start = res->start;
>  	end = res->end;
> +	BUG_ON(start >= end);

BUG_ON seems a little strong for bad arguments to the function but I am
ok with it. 

Thanks,
 Keith 


      reply	other threads:[~2006-08-04  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  3:34 [PATCH] memory hotadd fixes [3/5] find_next_system_ram catch range fix KAMEZAWA Hiroyuki
2006-08-04  0:08 ` keith mannthey [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=1154650093.5925.42.camel@keithlap \
    --to=kmannth@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=y-goto@jp.fujitsu.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox