linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	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: [PATCH] [BUGFIX] Avoid getting nid from invalid struct page at page_cgroup allocation (as Re: [Bugme-new] [Bug 36192] New: Kernel panic when boot the 2.6.39+ kernel based off of 2.6.32 kernel
Date: Thu, 9 Jun 2011 10:42:13 +0900	[thread overview]
Message-ID: <20110609104213.ac276d04.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20110609100434.64898575.kamezawa.hiroyu@jp.fujitsu.com>

On Thu, 9 Jun 2011 10:04:34 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:

> On Wed, 8 Jun 2011 12:15:11 +0200
> Johannes Weiner <hannes@cmpxchg.org> wrote:

> Thank you for review.

updated.
==

  reply	other threads:[~2011-06-09  1:49 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 ` 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
2011-06-09  1:04                                     ` KAMEZAWA Hiroyuki
2011-06-09  1:42                                       ` KAMEZAWA Hiroyuki [this message]
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=20110609104213.ac276d04.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=hannes@cmpxchg.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox