From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: "d.hatayama@jp.fujitsu.com" <d.hatayama@jp.fujitsu.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: makedumpfile: get_max_mapnr() from ELF header problem
Date: Wed, 19 Mar 2014 19:29:32 +0100 [thread overview]
Message-ID: <20140319192932.40310fac@holzheu> (raw)
In-Reply-To: <0910DD04CBD6DE4193FCF86B9C00BE971F7B95@BPXM01GP.gisp.nec.co.jp>
On Wed, 19 Mar 2014 07:14:25 +0000
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp> wrote:
> >Hello Atsushi,
> >
> >I debugged my problem a bit further and tried to implement
> >a function that gets the maximum page frame number from the
> >Linux kernel memory management structures.
> >
> >I am no memory management expert, so the following patch probably
> >is not complete, but at least for my setup it worked.
>
> The patch looks good for your case, but I don't think it's a proper
> approach for this problem.
>
> Now, I think this is a problem of get_mm_sparsemem() in makedumpfile.
> To say in more detail, the problem is "wrong calculating the address
> of unused mem_map".
>
> Looking at the log you sent, some addresses of mem_map corresponding
> to unused pages look invalid like below:
>
> mem_map (256)
> mem_map : 80000c0002018
> pfn_start : 1000000
> pfn_end : 1010000
> mem_map (257)
> mem_map : 800001840400000
> pfn_start : 1010000
> pfn_end : 1020000
> ...
> mem_map (544)
> mem_map : a82400012f14fffc
> pfn_start : 2200000
> pfn_end : 2210000
>
> ...(and more)
>
> However, makedumpfile should calculate such unused mem_map addresses
> as 0(NOT_MEMMAP_ADDR). Actually it works as expected at least in my
> environment(x86_64):
>
> ...
> mem_map (16)
> mem_map : 0
> pfn_start : 80000
> pfn_end : 88000
> mem_map (17)
> mem_map : 0
> pfn_start : 88000
> pfn_end : 90000
> ...
>
> makedumpfile get the address from mem_section.section_mem_map,
> it will be initialized with zero:
>
> [CONFIG_SPARSEMEM_EXTREAM]
> paging_init()
> sparse_memory_present_with_active_regions()
> memory_present()
> sparse_index_init()
> sparse_index_alloc() // allocate mem_section with kzalloc()
>
> makedumpfile assumes the value of unused mem_section will remain as 0,
> but I suspect this assumption may be broken in your environment.
>
Hello Atshushi,
I noticed that my last patch was not complete. It only checked the
mem_section[] array for zero entries. But as you noticed, we also
have to check the section array that we get from the mem_section
entries.
So I updated the patch.
Michael
---
makedumpfile.c | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
--- a/makedumpfile.c
+++ b/makedumpfile.c
@@ -2690,11 +2690,14 @@ nr_to_section(unsigned long nr, unsigned
{
unsigned long addr;
- if (is_sparsemem_extreme())
+ if (is_sparsemem_extreme()) {
+ if (mem_sec[SECTION_NR_TO_ROOT(nr)] == 0)
+ return NOT_KV_ADDR;
addr = mem_sec[SECTION_NR_TO_ROOT(nr)] +
(nr & SECTION_ROOT_MASK()) * SIZE(mem_section);
- else
+ } else {
addr = SYMBOL(mem_section) + (nr * SIZE(mem_section));
+ }
if (!is_kvaddr(addr))
return NOT_KV_ADDR;
@@ -2778,10 +2781,19 @@ get_mm_sparsemem(void)
}
for (section_nr = 0; section_nr < num_section; section_nr++) {
section = nr_to_section(section_nr, mem_sec);
- mem_map = section_mem_map_addr(section);
- mem_map = sparse_decode_mem_map(mem_map, section_nr);
- if (!is_kvaddr(mem_map))
+ if (section == NOT_KV_ADDR) {
mem_map = NOT_MEMMAP_ADDR;
+ } else {
+ mem_map = section_mem_map_addr(section);
+ if (mem_map == 0) {
+ mem_map = NOT_MEMMAP_ADDR;
+ } else {
+ mem_map = sparse_decode_mem_map(mem_map,
+ section_nr);
+ if (!is_kvaddr(mem_map))
+ mem_map = NOT_MEMMAP_ADDR;
+ }
+ }
pfn_start = section_nr * PAGES_PER_SECTION();
pfn_end = pfn_start + PAGES_PER_SECTION();
if (info->max_mapnr < pfn_end)
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-03-19 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 12:41 makedumpfile: get_max_mapnr() from ELF header problem Michael Holzheu
2014-03-03 3:11 ` Atsushi Kumagai
2014-03-03 9:44 ` Michael Holzheu
2014-03-11 6:22 ` Atsushi Kumagai
2014-03-11 11:35 ` Michael Holzheu
2014-03-12 4:15 ` HATAYAMA Daisuke
2014-03-12 6:01 ` Atsushi Kumagai
2014-03-12 16:18 ` Michael Holzheu
2014-03-14 8:54 ` Atsushi Kumagai
2014-03-14 14:19 ` Michael Holzheu
2014-03-19 7:14 ` Atsushi Kumagai
2014-03-19 18:29 ` Michael Holzheu [this message]
2014-03-20 10:23 ` Michael Holzheu
[not found] ` <20140319180903.2c6e2b72@holzheu>
2014-03-25 1:14 ` Atsushi Kumagai
2014-03-25 15:24 ` Michael Holzheu
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=20140319192932.40310fac@holzheu \
--to=holzheu@linux.vnet.ibm.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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