From: Christoph Lameter <clameter@sgi.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC/Patch](memory hotplug) fix null pointer access of kmem_cache_node after memory hotplug
Date: Wed, 19 Sep 2007 10:23:28 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709191021110.11138@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070919095823.3770.Y-GOTO@jp.fujitsu.com>
On Wed, 19 Sep 2007, Yasunori Goto wrote:
> build_zonelist() is called very early stage of bootstrap, But it is
> called final stage of hot-add.
> When build_zonelist() is called at hot-add, all kernel module can
> use new memory of the node. So, I'm afraid like following worst case.
>
> build_zonelist()
> : new_nodes_page = new_slab();
> : :
> : :
> : discard_slab(new_nodes_page)
> : (access kmem_cache_node)
> :
> kmem_cache_node setting,
So we cannot do this without holding off other kernel accesses since it is
not serialized like bootstrap. Sigh.
> > > I think this "delay creation" fix is better way than it.
> >
> > Looks like this is a way to on demand node structure creation?
>
> Yes.
Could be useful in general if you can make that work reliably. We can just
start out with a single per node structure for the boot node and then add
others on demand?
--
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>
next prev parent reply other threads:[~2007-09-19 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 12:33 Yasunori Goto
2007-09-18 19:05 ` Christoph Lameter
2007-09-19 2:12 ` Yasunori Goto
2007-09-19 17:23 ` Christoph Lameter [this message]
2007-09-20 2:06 ` Yasunori Goto
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=Pine.LNX.4.64.0709191021110.11138@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-mm@kvack.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