From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
akpm@linux-foundation.org
Cc: kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH][mmotm][BUGFIX] kcore use registered physmem information ia64-fix (Was Re: mmotm 2009-09-03-16-35 uploaded
Date: Fri, 11 Sep 2009 10:25:14 +0900 (JST) [thread overview]
Message-ID: <20090911102351.DB5F.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20090910115859.c2291eb8.kamezawa.hiroyu@jp.fujitsu.com>
> Ok, I confirmed this one fixes the issue.
mmotm-2009-09-09 + this patch booted successful on my box.
Tested-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Andrew, could you please pick it up?
> ==
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> kcore-use-registerd-physmem-information.patch registers physmem information
> based on ioresource. Then, this addition is unnecessary.
>
> Why panic:
> At boot, rebuilding kclist for physmem, all KCORE_RAM entries are kfreed.
> Because this ramaining one entires kclist of KCORE_RAM in kernel data area
> to ther list, this causes panic in kclist rebuilding which calls kfree().
>
> Reported-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> arch/ia64/mm/init.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> Index: mmotm-2.6.31-Sep3/arch/ia64/mm/init.c
> ===================================================================
> --- mmotm-2.6.31-Sep3.orig/arch/ia64/mm/init.c
> +++ mmotm-2.6.31-Sep3/arch/ia64/mm/init.c
> @@ -617,7 +617,6 @@ mem_init (void)
> long reserved_pages, codesize, datasize, initsize;
> pg_data_t *pgdat;
> int i;
> - static struct kcore_list kcore_mem;
>
> BUG_ON(PTRS_PER_PGD * sizeof(pgd_t) != PAGE_SIZE);
> BUG_ON(PTRS_PER_PMD * sizeof(pmd_t) != PAGE_SIZE);
> @@ -639,8 +638,6 @@ mem_init (void)
>
> high_memory = __va(max_low_pfn * PAGE_SIZE);
>
> - kclist_add(&kcore_mem, __va(0), max_low_pfn * PAGE_SIZE, KCORE_RAM);
> -
> for_each_online_pgdat(pgdat)
> if (pgdat->bdata->node_bootmem_map)
> totalram_pages += free_all_bootmem_node(pgdat);
>
next prev parent reply other threads:[~2009-09-11 1:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 23:40 akpm
2009-09-04 12:56 ` Dave Young
2009-09-04 23:17 ` Andrew Morton
2009-09-04 20:54 ` mount.nfs oops [was: mmotm 2009-09-03-16-35 uploaded] Jiri Slaby
2009-09-04 22:12 ` Trond Myklebust
2009-09-04 22:26 ` Jiri Slaby
2009-09-04 22:53 ` Trond Myklebust
2009-09-06 16:11 ` Jiri Slaby
2009-09-04 23:30 ` mmotm 2009-09-03-16-35 uploaded Randy Dunlap
2009-09-09 0:49 ` KOSAKI Motohiro
2009-09-09 1:14 ` KAMEZAWA Hiroyuki
2009-09-09 1:31 ` KAMEZAWA Hiroyuki
2009-09-10 1:39 ` KOSAKI Motohiro
2009-09-10 2:58 ` [PATCH][mmotm][BUGFIX] kcore use registered physmem information ia64-fix (Was " KAMEZAWA Hiroyuki
2009-09-11 1:25 ` KOSAKI Motohiro [this message]
2009-09-09 1:34 ` KOSAKI Motohiro
2009-09-09 7:35 ` Mel Gorman
2009-09-09 8:17 ` KOSAKI Motohiro
2009-09-09 8:47 ` Mel Gorman
2009-09-09 8:51 ` KOSAKI Motohiro
2009-09-09 9:31 ` Mel Gorman
2009-09-10 0:02 ` KOSAKI Motohiro
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=20090911102351.DB5F.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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
all inboxes | Powered by JetHome®