linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Xishi Qiu <qiuxishi@huawei.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tang Chen <tangchen@cn.fujitsu.com>,
	Yinghai Lu <yinghai@kernel.org>, 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>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: node-hotplug: is memset 0 safe in try_offline_node()?
Date: Thu, 5 Mar 2015 17:39:09 +0800	[thread overview]
Message-ID: <54F8243D.7020809@huawei.com> (raw)
In-Reply-To: <54F81322.8010202@cn.fujitsu.com>

On 2015/3/5 16:26, Gu Zheng wrote:

> Hi Xishi,
> Could you please try the following one?
> It postpones the reset of obsolete pgdat from try_offline_node() to
> hotadd_new_pgdat(), and just resetting pgdat->nr_zones and
> pgdat->classzone_idx to be 0 rather than the whole reset by memset()
> as Kame suggested.
> 
> Regards,
> Gu
> 
> ---
>  mm/memory_hotplug.c |   13 ++++---------
>  1 files changed, 4 insertions(+), 9 deletions(-)
> 
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 1778628..c17eebf 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -1092,6 +1092,10 @@ static pg_data_t __ref *hotadd_new_pgdat(int nid, u64 start)
>  			return NULL;
>  
>  		arch_refresh_nodedata(nid, pgdat);
> +	} else {
> +		/* Reset the nr_zones and classzone_idx to 0 before reuse */
> +		pgdat->nr_zones = 0;
> +		pgdat->classzone_idx = 0;

Hi Gu,

This is just to avoid the warning, I think it's no meaning.
Here is the changlog from the original patch:

commit 88fdf75d1bb51d85ba00c466391770056d44bc03
    ...
    Warn if memory-hotplug/boot code doesn't initialize pg_data_t with zero
    when it is allocated.  Arch code and memory hotplug already initiailize
    pg_data_t.  So this warning should never happen.  I select fields *randomly*
    near the beginning, middle and end of pg_data_t for checking.
    ...

Thanks,
Xishi Qiu

>  	}
>  
>  	/* we can use NODE_DATA(nid) from here */
> @@ -2021,15 +2025,6 @@ void try_offline_node(int nid)
>  
>  	/* notify that the node is down */
>  	call_node_notify(NODE_DOWN, (void *)(long)nid);
> -
> -	/*
> -	 * Since there is no way to guarentee the address of pgdat/zone is not
> -	 * on stack of any kernel threads or used by other kernel objects
> -	 * without reference counting or other symchronizing method, do not
> -	 * reset node_data and free pgdat here. Just reset it to 0 and reuse
> -	 * the memory when the node is online again.
> -	 */
> -	memset(pgdat, 0, sizeof(*pgdat));
>  }
>  EXPORT_SYMBOL(try_offline_node);
>  



--
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-05  9:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  3:30 node-hotplug: is memset 0 safe in try_offline_node()? Xishi Qiu
2015-03-03 10:20 ` 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 [this message]
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=54F8243D.7020809@huawei.com \
    --to=qiuxishi@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@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).