linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: 2.6.27-rc8 hot memory remove panic
Date: Fri, 03 Oct 2008 12:15:57 +0900	[thread overview]
Message-ID: <20081003115721.38C0.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <1222985880.3419.20.camel@badari-desktop>

> On Thu, 2008-10-02 at 10:23 -0700, Badari Pulavarty wrote:
> > Hi,
> > 
> > Ran into this while testing hotplug memory remove on 2.6.27-rc8.
> > Never saw this earlier.
> > 
> > Any ideas on whats happening.
> > 
> > put_page_bootmem():
> >         BUG_ON(type >= -1);
> 
> 
> It looks like we have undocumented dependency on CONFIG_NUMA=y to get
> hotplug memory remove working.
> 
> register_page_bootmem_info_node() gets called only if 
> CONFIG_NEED_MULTIPLE_NODES=y which gets selected only if CONFIG_NUMA=y.

Oops. My bad....

I remember its dependency is removed from Kconfig some month ago.
Then, register_page_bootmem_info_node() should be called when CONFIG_NUMA
is off.
Is this patch enough?

---

register_page_bootmem_info_node() should be called for memory hot-remove
even when CONFIG_NUMA is off.

Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com>

---
 mm/bootmem.c |    1 +
 1 file changed, 1 insertion(+)

Index: current/mm/bootmem.c
===================================================================
--- current.orig/mm/bootmem.c	2008-10-03 09:58:58.000000000 +0900
+++ current/mm/bootmem.c	2008-10-03 11:57:21.000000000 +0900
@@ -222,6 +222,7 @@ unsigned long __init free_all_bootmem_no
  */
 unsigned long __init free_all_bootmem(void)
 {
+	register_page_bootmem_info_node(NODE_DATA(0));
 	return free_all_bootmem_core(NODE_DATA(0)->bdata);
 }
 

-- 
Yasunori Goto 


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2008-10-03  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 17:23 Badari Pulavarty
2008-10-02 22:18 ` Badari Pulavarty
2008-10-03  3:15   ` Yasunori Goto [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=20081003115721.38C0.E1E9C6FF@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=pbadari@gmail.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