All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Mel Gorman <mgorman@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, qcui@redhat.com,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [Bugme-new] [Bug 36192] New: Kernel panic when boot the 2.6.39+ kernel based off of 2.6.32 kernel
Date: Wed, 8 Jun 2011 12:15:11 +0200	[thread overview]
Message-ID: <20110608101511.GD17886@cmpxchg.org> (raw)
In-Reply-To: <20110608174505.e4be46d6.kamezawa.hiroyu@jp.fujitsu.com>

On Wed, Jun 08, 2011 at 05:45:05PM +0900, KAMEZAWA Hiroyuki wrote:
> @@ -196,7 +195,11 @@ static int __meminit init_section_page_cgroup(unsigned long pfn)
>  		pc = base + index;
>  		init_page_cgroup(pc, nr);
>  	}
> -
> +	/*
> +	 * Even if passed 'pfn' is not aligned to section, we need to align
> +	 * it to section boundary because of SPARSEMEM pfn calculation.
> +	 */
> +	pfn = pfn & ~(PAGES_PER_SECTION - 1);

PAGE_SECTION_MASK?

>  	section->page_cgroup = base - pfn;
>  	total_usage += table_size;
>  	return 0;
> @@ -228,7 +231,7 @@ int __meminit online_page_cgroup(unsigned long start_pfn,
>  	for (pfn = start; !fail && pfn < end; pfn += PAGES_PER_SECTION) {
>  		if (!pfn_present(pfn))
>  			continue;
> -		fail = init_section_page_cgroup(pfn);
> +		fail = init_section_page_cgroup(pfn, nid);

AFAICS, nid can be -1 in the hotplug callbacks when there is a new
section added to a node that already has memory, and then the
allocation will fall back to numa_node_id().

So I think we either need to trust start_pfn has valid mem map backing
it (ARM has no memory hotplug support) and use pfn_to_nid(start_pfn),
or find another way to the right node, no?

> @@ -285,14 +288,36 @@ void __init page_cgroup_init(void)
>  {
>  	unsigned long pfn;
>  	int fail = 0;
> +	int nid;
>  
>  	if (mem_cgroup_disabled())
>  		return;
>  
> -	for (pfn = 0; !fail && pfn < max_pfn; pfn += PAGES_PER_SECTION) {
> -		if (!pfn_present(pfn))
> -			continue;
> -		fail = init_section_page_cgroup(pfn);
> +	for_each_node_state(nid, N_HIGH_MEMORY) {
> +		unsigned long start_pfn, end_pfn;
> +
> +		start_pfn = NODE_DATA(nid)->node_start_pfn;
> +		end_pfn = start_pfn + NODE_DATA(nid)->node_spanned_pages;
> +		/*
> +		 * Because we cannot trust page->flags of page out of node
> +		 * boundary, we skip pfn < start_pfn.
> +		 */
> +		for (pfn = start_pfn;
> +		     !fail && (pfn < end_pfn);
> +		     pfn = ALIGN(pfn + 1, PAGES_PER_SECTION)) {

If we don't bother to align the pfn on the first iteration, I don't
think we should for subsequent iterations.  init_section_page_cgroup()
has to be able to cope anyway.  How about

	pfn += PAGES_PER_SECTION

instead?

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2011-06-08 10:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36192-10286@https.bugzilla.kernel.org/>
2011-05-30  6:19 ` [Bugme-new] [Bug 36192] New: Kernel panic when boot the 2.6.39+ kernel based off of 2.6.32 kernel Andrew Morton
2011-05-30  7:01   ` KAMEZAWA Hiroyuki
2011-05-30  7:12     ` Minchan Kim
2011-05-30  7:29     ` KAMEZAWA Hiroyuki
2011-05-30  7:54       ` KAMEZAWA Hiroyuki
2011-05-30  8:51         ` KAMEZAWA Hiroyuki
2011-06-06 12:54           ` Johannes Weiner
2011-06-06 21:45             ` Andrew Morton
2011-06-06 23:45               ` KAMEZAWA Hiroyuki
2011-06-07  8:45                 ` Mel Gorman
2011-06-07  8:43                   ` KAMEZAWA Hiroyuki
2011-06-07  9:09                     ` Mel Gorman
2011-06-07  9:33                       ` KAMEZAWA Hiroyuki
2011-06-07 10:18                         ` Mel Gorman
2011-06-07 23:40                           ` KAMEZAWA Hiroyuki
2011-06-08  0:42                             ` KAMEZAWA Hiroyuki
2011-06-08  7:43                               ` Mel Gorman
2011-06-08  8:45                                 ` KAMEZAWA Hiroyuki
2011-06-08  9:03                                   ` Mel Gorman
2011-06-08 10:15                                   ` Johannes Weiner [this message]
2011-06-09  1:04                                     ` KAMEZAWA Hiroyuki
2011-06-09  1:42                                       ` [PATCH] [BUGFIX] Avoid getting nid from invalid struct page at page_cgroup allocation (as " KAMEZAWA Hiroyuki
2011-06-07  0:57               ` KAMEZAWA Hiroyuki
2011-06-07  7:51                 ` Johannes Weiner
2011-06-07  7:55                   ` KAMEZAWA Hiroyuki
2011-06-07 10:26                     ` Johannes Weiner
2011-06-07 23:45                       ` KAMEZAWA Hiroyuki
2011-06-08  9:33                         ` Johannes Weiner
2011-06-07  9:03                 ` Mel Gorman
2011-06-07  9:06                   ` KAMEZAWA Hiroyuki
2011-06-07 10:13                     ` Mel Gorman
2011-06-07  8:37             ` Mel Gorman

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=20110608101511.GD17886@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mgorman@suse.de \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=qcui@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.