linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Xishi Qiu <qiuxishi@huawei.com>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Yinghai Lu <yinghai@kernel.org>
Cc: Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Toshi Kani <toshi.kani@hp.com>, Mel Gorman <mgorman@suse.de>,
	Tejun Heo <tj@kernel.org>
Subject: node-hotplug: is memset 0 safe in try_offline_node()?
Date: Tue, 3 Mar 2015 11:30:23 +0800	[thread overview]
Message-ID: <54F52ACF.4030103@huawei.com> (raw)

When hot-remove a numa node, we will clear pgdat,
but is memset 0 safe in try_offline_node()?

process A:			offline node XX:
for_each_populated_zone()
find online node XX
cond_resched()
				offline cpu and memory, then try_offline_node()
				node_set_offline(nid), and memset(pgdat, 0, sizeof(*pgdat))
access node XX's pgdat
NULL pointer access error

Thanks,
Xishi Qiu

--
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:[~2015-03-03  3:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  3:30 Xishi Qiu [this message]
2015-03-03 10:20 ` node-hotplug: is memset 0 safe in try_offline_node()? Gu Zheng
2015-03-04  2:22   ` Xishi Qiu
2015-03-04  2:52     ` Xishi Qiu
2015-03-04  3:56       ` Gu Zheng
2015-03-04  8:03         ` Xishi Qiu
2015-03-04  8:53           ` Kamezawa Hiroyuki
2015-03-04  9:53             ` Gu Zheng
2015-03-04  3:53     ` Gu Zheng
2015-03-04  7:01       ` Xishi Qiu
2015-03-04  8:31       ` Xie XiuQi
2015-03-05  8:26 ` Gu Zheng
2015-03-05  9:39   ` Xishi Qiu
2015-03-05  9:45     ` Gu Zheng
2015-03-11  1:12     ` Gu Zheng
2015-03-11  2:51       ` Xie XiuQi

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=54F52ACF.4030103@huawei.com \
    --to=qiuxishi@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=tangchen@cn.fujitsu.com \
    --cc=tj@kernel.org \
    --cc=toshi.kani@hp.com \
    --cc=yinghai@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 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).