linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Matt Fleming
	<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
	<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] x86/efi: Add necessary checks before iterating over efi.memmap
Date: Tue, 13 Sep 2016 19:26:22 +0800	[thread overview]
Message-ID: <20160913112622.GA25947@localhost.localdomain> (raw)
In-Reply-To: <CAKv+Gu_NrMGSu-9DxyZdurLWNbkHx2D480WS3gupazzC8U67EQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Sep 13, 2016 at 09:51:39AM +0100, Ard Biesheuvel wrote:
>On 13 September 2016 at 04:28, Chao Gao <chao.gao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
>> Commit 78ce248f (efi: Iterate over efi.memmap in for_each_efi_memory_desc())
>> replaces the old loop by for_each_efi_memory_desc() which will encounter #PF
>> when efi.memap are not initialized.
>>
>> In boot process, xen set EFI_PARAVIRT in xen_efi_init() before setup_arch()
>> is called. This leads efi_memmap_init() will not initialize structures
>> related to efi.memmap. However, the following functions e.g.
>> efi_find_mirror(), efi_print_memmap() and efi_free_boot_services() access
>> efi.memmap without necessary checks. kernel and xen crash in this case.
>> After adding these checks, xen and kernel boot up normally.
>>
>
>OK, so looking at the hunks below, it looks to me like we should
>initialize the efi.memmap to sane values in the EFI_PARAVIRT case,
>rather than open coding this test each time for_each_efi_memory_desc()
>is invoked.
>

Ard, thanks for you reply.
Yes, I think what you say is also a solution. This patch just uses the same method
using by some existed functions such as efi_memblock_x86_reserve_range() and 
efi_runtime_init(). we can handle cases with existed flags correctly and the checks
seems not too much. Maybe we can try what you say when it's really needed.

>> Signed-off-by: Chao Gao <chao.gao-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
>> ---
>>  arch/x86/platform/efi/efi.c    | 6 ++++++
>>  arch/x86/platform/efi/quirks.c | 3 +++
>>  2 files changed, 9 insertions(+)
>>
>> diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
>> index 1fbb408..68966dc 100644
>> --- a/arch/x86/platform/efi/efi.c
>> +++ b/arch/x86/platform/efi/efi.c
>> @@ -102,6 +102,9 @@ void __init efi_find_mirror(void)
>>         efi_memory_desc_t *md;
>>         u64 mirror_size = 0, total_size = 0;
>>
>> +       if (efi_enabled(EFI_PARAVIRT))
>> +               return;
>> +
>>         for_each_efi_memory_desc(md) {
>>                 unsigned long long start = md->phys_addr;
>>                 unsigned long long size = md->num_pages << EFI_PAGE_SHIFT;
>> @@ -207,6 +210,9 @@ void __init efi_print_memmap(void)
>>         efi_memory_desc_t *md;
>>         int i = 0;
>>
>> +       if (efi_enabled(EFI_PARAVIRT))
>> +               return;
>> +
>>         for_each_efi_memory_desc(md) {
>>                 char buf[64];
>>
>> diff --git a/arch/x86/platform/efi/quirks.c b/arch/x86/platform/efi/quirks.c
>> index 89d1146..4fa1e4d 100644
>> --- a/arch/x86/platform/efi/quirks.c
>> +++ b/arch/x86/platform/efi/quirks.c
>> @@ -251,6 +251,9 @@ void __init efi_free_boot_services(void)
>>  {
>>         efi_memory_desc_t *md;
>>
>> +       if (efi_enabled(EFI_PARAVIRT))
>> +               return;
>> +
>>         for_each_efi_memory_desc(md) {
>>                 unsigned long long start = md->phys_addr;
>>                 unsigned long long size = md->num_pages << EFI_PAGE_SHIFT;
>> --
>> 1.8.3.1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-efi" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-09-13 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13  3:28 [PATCH] x86/efi: Add necessary checks before iterating over efi.memmap Chao Gao
     [not found] ` <20160913032813.GA11652-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-09-13  8:51   ` Ard Biesheuvel
     [not found]     ` <CAKv+Gu_NrMGSu-9DxyZdurLWNbkHx2D480WS3gupazzC8U67EQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-13 11:26       ` Chao Gao [this message]
2016-09-20  5:25 ` Chao Gao
2016-09-20  9:56   ` Matt Fleming

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=20160913112622.GA25947@localhost.localdomain \
    --to=chao.gao-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
    --cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).