From: joeyli <jlee@suse.com>
To: Dave Young <dyoung@redhat.com>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-efi@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Randy Wright <rwright@hpe.com>, Ingo Molnar <mingo@redhat.com>,
akpm@linux-foundation.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] efi: Fix the size not consistent issue when unmapping memory map
Date: Mon, 16 Apr 2018 14:34:14 +0800 [thread overview]
Message-ID: <20180416063414.GG16023@linux-l9pv.suse> (raw)
In-Reply-To: <20180416025734.GA26685@dhcp-128-65.nay.redhat.com>
On Mon, Apr 16, 2018 at 10:57:34AM +0800, Dave Young wrote:
> On 04/13/18 at 02:27pm, Lee, Chun-Yi wrote:
> > When using kdump, SOMETIMES the "size not consistent" warning message
> > shows up when the crash kernel boots with early_ioremap_debug parameter:
> >
> > WARNING: CPU: 0 PID: 0 at ../mm/early_ioremap.c:182 early_iounmap+0x4f/0x12c()
> > early_iounmap(ffffffffff200180, 00000118) [0] size not consistent 00000120
> >
> > The root cause is that the unmapping size of memory map doesn't
> > match with the original size when mapping:
> >
> > in __efi_memmap_init()
> > map.map = early_memremap(phys_map, data->size);
> >
> > in efi_memmap_unmap()
> > size = efi.memmap.desc_size * efi.memmap.nr_map;
> > early_memunmap(efi.memmap.map, size);
> >
> > But the efi.memmap.nr_map is from __efi_memmap_init(). The remainder
> > of size was discarded when calculating the nr_map:
> > map.nr_map = data->size / data->desc_size;
> >
> > When the original size of memory map region does not equal to the
> > result of multiplication. The "size not consistent" warning
> > will be triggered.
> >
> > This issue sometimes was hit by kdump because kexec set the efi map
> > size to align with 16 when loading crash kernel image:
> >
> > in bzImage64_load()
> > efi_map_sz = efi_get_runtime_map_size();
> > efi_map_sz = ALIGN(efi_map_sz, 16);
> >
> > This patch changes the logic in the unmapping function. Using the
> > end address of map to calcuate original size.
> >
> > Thank Randy Wright for his report and testing. And also thank
> > Takashi Iwai for his help to trace issue.
>
> Good catch. The kexec code need to be fixed to use a separate buffer so
> avoid the alignment like what kexec-tools did. I can submit a fix for
> that.
>
Thanks!
> But this issue could be a potential issue even if kexec get fixed so it
> looks worth a fix in efi code as well. How about mapping only nr_maps
> *desc_size in __efi_memmap_init? It looks easier to understand.
>
Takashi has another patch as you said. Finally I sent this patch because
it's smaller.
Thanks a lot!
Joey Lee
next prev parent reply other threads:[~2018-04-16 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 6:27 [PATCH] efi: Fix the size not consistent issue when unmapping memory map Lee, Chun-Yi
2018-04-16 2:57 ` Dave Young
2018-04-16 3:09 ` Dave Young
2018-04-16 6:37 ` joeyli
2018-04-17 0:35 ` Randy Wright
2018-04-17 1:20 ` joeyli
2018-04-17 2:41 ` Dave Young
2018-04-17 20:34 ` Randy Wright
2018-04-16 6:34 ` joeyli [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-02 6:17 Lee, Chun-Yi
2018-05-03 12:05 ` Ard Biesheuvel
2018-05-04 7:29 ` joeyli
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=20180416063414.GG16023@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=dyoung@redhat.com \
--cc=joeyli.kernel@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rwright@hpe.com \
--cc=tiwai@suse.de \
--cc=vgoyal@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