From: joeyli <jlee@suse.com>
To: Randy Wright <rwright@hpe.com>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
linux-efi@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Takashi Iwai <tiwai@suse.de>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
akpm@linux-foundation.org, Vivek Goyal <vgoyal@redhat.com>,
Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH] efi: Fix the size not consistent issue when unmapping memory map
Date: Tue, 17 Apr 2018 09:20:48 +0800 [thread overview]
Message-ID: <20180417012048.GK16023@linux-l9pv.suse> (raw)
In-Reply-To: <20180417003522.GA2741@rfwz>
On Mon, Apr 16, 2018 at 06:35:22PM -0600, Randy Wright wrote:
> On Mon, Apr 16, 2018 at 02:37:38PM +0800, joeyli wrote:
> > Hi Randy,
> > ...
> > Randy, do you want to try Dave's kexec patch on your environment? Please remove
> > my patch first.
> >
> > Thanks a lot!
> > Joey Lee
>
> Hi Joey,
>
> I tried Dave's patch to kexec-bzimage64.c on my build of the SuSE
> 4.12.14-15 kernel. I ran the same test as I did with your patch: I
> verified the early_ioremap.c warnings occurred with a crash triggered
> from a kexec boot of the unmodified kernel. Then I applied the patch to
> kexec-bzimage64.c, rebuilt, re-ran the test to crash from the kexec'ed
> kernel, and verified the warnings are no longer seen.
>
Thanks for your help! Looks that Dave's kexec patch works to prevent the
warning message.
> I'm out of time today, but I will plan to run the same test tomorrow on
> a build of the SuSE 4.4.120-94.17 kernel, on which I had also reported
> the original bug.
>
Both kexec and efi sides will be applied patches.
Thanks a lot!
Joey Lee
next prev parent reply other threads:[~2018-04-17 1:20 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 [this message]
2018-04-17 2:41 ` Dave Young
2018-04-17 20:34 ` Randy Wright
2018-04-16 6:34 ` joeyli
-- 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=20180417012048.GK16023@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