From: Dave Young <dyoung@redhat.com>
To: Kairui Song <kasong@redhat.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com, x86@kernel.org,
bhe@redhat.com, kexec@lists.infradead.org,
akpm@linux-foundation.org, robert.moore@intel.com,
erik.schmauss@intel.com, rafael.j.wysocki@intel.com,
lenb@kernel.org, fanc.fnst@cn.fujitsu.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v3 1/3] x86, kexec_file_load: Don't setup EFI info if EFI runtime is not enabled
Date: Fri, 25 Jan 2019 10:53:46 +0800 [thread overview]
Message-ID: <20190125025346.GA19241@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <20190118111310.29589-2-kasong@redhat.com>
On 01/18/19 at 07:13pm, Kairui Song wrote:
> Currently with "efi=noruntime" in kernel command line, calling
> kexec_file_load will raise below problem:
>
> [ 97.967067] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
> [ 97.967894] #PF error: [normal kernel read fault]
> ...
> [ 97.980456] Call Trace:
> [ 97.980724] efi_runtime_map_copy+0x28/0x30
> [ 97.981267] bzImage64_load+0x688/0x872
> [ 97.981794] arch_kexec_kernel_image_load+0x6d/0x70
> [ 97.982441] kimage_file_alloc_init+0x13e/0x220
> [ 97.983035] __x64_sys_kexec_file_load+0x144/0x290
> [ 97.983586] do_syscall_64+0x55/0x1a0
> [ 97.983962] entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> When efi runtime is not enabled, efi memmap is not mapped, so just skip
> EFI info setup.
>
> Suggested-by: Dave Young <dyoung@redhat.com>
> Signed-off-by: Kairui Song <kasong@redhat.com>
> ---
> arch/x86/kernel/kexec-bzimage64.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/x86/kernel/kexec-bzimage64.c b/arch/x86/kernel/kexec-bzimage64.c
> index 2c007abd3d40..097f52fb02e3 100644
> --- a/arch/x86/kernel/kexec-bzimage64.c
> +++ b/arch/x86/kernel/kexec-bzimage64.c
> @@ -167,6 +167,9 @@ setup_efi_state(struct boot_params *params, unsigned long params_load_addr,
> struct efi_info *current_ei = &boot_params.efi_info;
> struct efi_info *ei = ¶ms->efi_info;
>
> + if (!efi_enabled(EFI_RUNTIME_SERVICES))
> + return 0;
> +
> if (!current_ei->efi_memmap_size)
> return 0;
>
> --
> 2.20.1
>
Patch 1/3 looks good to me, 2-3 should depend on Chao's early rsdp parsing according
to Boris.
Acked-by: Dave Young <dyoung@redhat.com>
Thanks
Dave
next prev parent reply other threads:[~2019-01-25 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 11:13 [PATCH v3 0/3] make kexec work with efi=noruntime or efi=old_map Kairui Song
2019-01-18 11:13 ` [PATCH v3 1/3] x86, kexec_file_load: Don't setup EFI info if EFI runtime is not enabled Kairui Song
2019-01-25 2:53 ` Dave Young [this message]
2019-01-18 11:13 ` [PATCH v3 2/3] acpi: store acpi_rsdp address for later kexec usage Kairui Song
2019-01-18 11:26 ` Borislav Petkov
2019-01-18 11:43 ` Kairui Song
2019-01-18 11:13 ` [PATCH v3 3/3] x86, kexec_file_load: make it work with efi=noruntime or efi=old_map Kairui Song
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=20190125025346.GA19241@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=erik.schmauss@intel.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).