From: Randy Wright <rwright@hpe.com>
To: joeyli <jlee@suse.com>, dyoung@redhat.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 14:34:05 -0600 [thread overview]
Message-ID: <20180417203405.GA4574@rfwz> (raw)
In-Reply-To: <20180417003522.GA2741@rfwz>
On Mon, Apr 16, 2018 at 06:35:22PM -0600, Randy Wright wrote:
> ... 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.
I carried out the test on the older kernel today. I found the version of
arch/x86/kernel/kexec-bzimage64.c in the SuSE kernel version
4.4.120-94.17 was sufficiently different from the newer version that one
chunk of the patch under discussion was rejected. Specifically, the
'struct kexec_buf kbuf' is not found in that older SuSE version of
kexec-bzimage64.c. But I made the same modification to the
calculation of variable params_misc_sz in the older source, ran the same
test, and there were no longer any warnings from early_ioremap.c.
--
Randy Wright Hewlett Packard Enterprise
Phone: (970) 898-0998 Mail: rwright@hpe.com
next prev parent reply other threads:[~2018-04-17 20: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 [this message]
2018-04-16 6:34 ` joeyli
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=20180417203405.GA4574@rfwz \
--to=rwright@hpe.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=dyoung@redhat.com \
--cc=jlee@suse.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=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;
as well as URLs for NNTP newsgroup(s).