From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"d.hatayama@jp.fujitsu.com" <d.hatayama@jp.fujitsu.com>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Subject: Re: [PATCH 2/2] makedumpfile: Use max_pfn from mem_map array
Date: Fri, 28 Mar 2014 17:46:22 +0100 [thread overview]
Message-ID: <20140328174622.2896296e@holzheu> (raw)
In-Reply-To: <20140328120047.24a056ea@hananiah.suse.cz>
On Fri, 28 Mar 2014 12:00:47 +0100
Petr Tesarik <ptesarik@suse.cz> wrote:
> On Thu, 27 Mar 2014 14:54:41 +0100
> Michael Holzheu <holzheu@linux.vnet.ibm.com> wrote:
[snip]
> > > >Here the fixed patch:
> > >
> > > Thanks, I'll merge the fixed version into v1.5.6.
> >
> > Great!
>
> I'm sorry to spoil the party, but this patch broke Xen dumps for me.
> I'm getting an long series of these messages:
>
> set_bitmap: Can't read the bitmap(/tmp/kdump_bitmap91pbsO). Invalid argument
> set_bitmap: Can't read the bitmap(/tmp/kdump_bitmap91pbsO). Invalid argument
> set_bitmap: Can't read the bitmap(/tmp/kdump_bitmap91pbsO). Invalid argument
> ...
>
> In fact, it most likely broke all non-cyclic dumps.
>
> That's because the bitmap length is calculated in prepare_bitmap_buffer
> using info->max_mapnr, but create_1st_bitmap() still loops over all
> PT_LOAD segments, calling set_bit_on_1st_bitmap() for each PFN. The
> offset may easily fall beyond the bitmap size.
What about the following patch. It works for me when I specify
the "--non-cyclic" option.
Michael
---
[PATCH] makedumpfile: Fix bitmap create for adjusted info->max_mapnr
If info->max_mapnr has been adjusted, for example because the dumped
system has specified the "mem=" kernel parameter, makedumpfile writes
the following error messages for Xen dumps or when the "--non-cyclic"
option has been specified:
set_bitmap: Can't read the bitmap(/tmp/kdump_bitmap96s9V8). Success
Fix this and consider "info->max_mapnr" in the create bitmap functions.
Signed-off-by: Michael Holzheu <holzheu@linux.vnet.ibm.com>
---
makedumpfile.c | 9 +++++++++
1 file changed, 9 insertions(+)
--- a/makedumpfile.c
+++ b/makedumpfile.c
@@ -4402,6 +4402,9 @@ create_1st_bitmap(void)
pfn_start = paddr_to_pfn(phys_start);
pfn_end = paddr_to_pfn(phys_end);
+ if (pfn_start > info->max_mapnr)
+ continue;
+ pfn_end = MIN(phys_end, info->max_mapnr);
for (pfn = pfn_start; pfn < pfn_end; pfn++) {
set_bit_on_1st_bitmap(pfn);
@@ -7511,6 +7514,9 @@ exclude_xen3_user_domain(void)
pfn = paddr_to_pfn(phys_start);
pfn_end = paddr_to_pfn(phys_end);
size = pfn_end - pfn;
+ if (pfn > info->max_mapnr)
+ continue;
+ pfn_end = MIN(phys_end, info->max_mapnr);
for (j = 0; pfn < pfn_end; pfn++, j++) {
print_progress(PROGRESS_XEN_DOMAIN, j + (size * i),
@@ -7575,6 +7581,9 @@ exclude_xen4_user_domain(void)
pfn = paddr_to_pfn(phys_start);
pfn_end = paddr_to_pfn(phys_end);
size = pfn_end - pfn;
+ if (pfn > info->max_mapnr)
+ continue;
+ pfn_end = MIN(phys_end, info->max_mapnr);
for (j = 0; pfn < pfn_end; pfn++, j++) {
print_progress(PROGRESS_XEN_DOMAIN, j + (size * i),
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-03-28 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 16:14 [PATCH 2/2] makedumpfile: Use max_pfn from mem_map array Michael Holzheu
2014-03-26 9:55 ` HATAYAMA Daisuke
2014-03-26 17:54 ` Michael Holzheu
2014-03-27 5:19 ` Atsushi Kumagai
2014-03-27 13:54 ` Michael Holzheu
2014-03-28 11:00 ` Petr Tesarik
2014-03-28 15:54 ` Michael Holzheu
2014-03-28 16:46 ` Michael Holzheu [this message]
2014-03-28 16:53 ` Petr Tesarik
2014-03-31 9:48 ` Atsushi Kumagai
2014-03-31 10:37 ` Petr Tesarik
2014-04-01 5:06 ` Atsushi Kumagai
2014-04-01 8:11 ` Petr Tesarik
2014-04-01 9:20 ` Michael Holzheu
2014-04-03 2:38 ` Atsushi Kumagai
2014-03-31 12:59 ` Michael Holzheu
2014-03-31 10:27 ` Petr Tesarik
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=20140328174622.2896296e@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 \
--cc=ptesarik@suse.cz \
/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