From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.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 17:45:05 +0900 [thread overview]
Message-ID: <20110608174505.e4be46d6.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20110608074350.GP5247@suse.de>
On Wed, 8 Jun 2011 08:43:50 +0100
Mel Gorman <mgorman@suse.de> wrote:
> On Wed, Jun 08, 2011 at 09:42:19AM +0900, KAMEZAWA Hiroyuki wrote:
> > On Wed, 8 Jun 2011 08:40:34 +0900
> > <SNIP>
>
> Missing a subject
>
> >
> > With sparsemem, page_cgroup_init scans pfn from 0 to max_pfn.
> > But this may scan a pfn which is not on any node and can access
> > memmap which is not initialized.
> >
> > This makes page_cgroup_init() for SPARSEMEM node aware and remove
> > a code to get nid from page->flags. (Then, we'll use valid NID
> > always.)
> >
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> > mm/page_cgroup.c | 41 +++++++++++++++++++++++++++++++++--------
> > 1 file changed, 33 insertions(+), 8 deletions(-)
> >
> > Index: linux-3.0-rc1/mm/page_cgroup.c
> > ===================================================================
> > --- linux-3.0-rc1.orig/mm/page_cgroup.c
> > +++ linux-3.0-rc1/mm/page_cgroup.c
> > @@ -162,21 +162,25 @@ static void free_page_cgroup(void *addr)
> > }
> > #endif
> >
> > -static int __meminit init_section_page_cgroup(unsigned long pfn)
> > +static int __meminit init_section_page_cgroup(unsigned long pfn, int nid)
> > {
> > struct page_cgroup *base, *pc;
> > struct mem_section *section;
> > unsigned long table_size;
> > unsigned long nr;
> > - int nid, index;
> > + int index;
> >
> > + /*
> > + * Even if passed 'pfn' is not aligned to section, we need to align
> > + * it to section boundary because of SPARSEMEM pfn calculation.
> > + */
> > + pfn = ALIGN(pfn, PAGES_PER_SECTION);
> > nr = pfn_to_section_nr(pfn);
>
> This comment is a bit opaque and from the context of the patch,
> it's hard to know why the alignment is necessary. At least move the
> alignment to beside where section->page_cgroup is set because it'll
> be easier to understand what is going on and why.
>
ok.
> > section = __nr_to_section(nr);
> >
> > if (section->page_cgroup)
> > return 0;
> >
> > - nid = page_to_nid(pfn_to_page(pfn));
> > table_size = sizeof(struct page_cgroup) * PAGES_PER_SECTION;
> > base = alloc_page_cgroup(table_size, nid);
> >
> > @@ -228,7 +232,7 @@ int __meminit online_page_cgroup(unsigne
> > 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);
> > }
> > if (!fail)
> > return 0;
> > @@ -285,14 +289,35 @@ void __init page_cgroup_init(void)
> > {
> > unsigned long pfn;
> > int fail = 0;
> > + int node;
> >
>
> Very nit-picky but you sometimes use node and sometimes use nid.
> Personally, nid is my preferred choice of name as its meaning is
> unambigious.
>
ok.
> > 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(node, N_HIGH_MEMORY) {
> > + unsigned long start_pfn, end_pfn;
> > +
> > + start_pfn = NODE_DATA(node)->node_start_pfn;
> > + end_pfn = start_pfn + NODE_DATA(node)->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 + PAGES_PER_SECTION, PAGES_PER_SECTION)) {
> > + if (!pfn_present(pfn))
> > + continue;
>
> Why did you not use pfn_valid()?
>
> pfn_valid checks a section has SECTION_HAS_MEM_MAP
> pfn_present checks a section has SECTION_MARKED_PRESENT
>
> SECTION_MARKED_PRESENT does not necessarily mean mem_map has been
> allocated although I admit that this is somewhat unlikely. I'm just
> curious if you had a reason for avoiding pfn_valid()?
>
hm, maybe I misunderstand some. I'll use pfn_valid().
> > + /*
> > + * Nodes can be overlapped
> > + * We know some arch can have nodes layout as
> > + * -------------pfn-------------->
> > + * N0 | N1 | N2 | N0 | N1 | N2 |.....
> > + */
> > + if (pfn_to_nid(pfn) != node)
> > + continue;
> > + fail = init_section_page_cgroup(pfn, node);
> > + }
> > }
> > if (fail) {
> > printk(KERN_CRIT "try 'cgroup_disable=memory' boot option\n");
> >
>
> FWIW, overall I think this is heading in the right direction.
>
Thank you. and I noticed I misunderstood what ALIGN() does.
This patch is made agaisnt the latest mainline git tree.
Tested on my host, at least.
==
next prev parent reply other threads:[~2011-06-08 8:52 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 [this message]
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 ` [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=20110608174505.e4be46d6.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