public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	izumi.taku@jp.fujitsu.com, fanc.fnst@cn.fujitsu.com,
	Thomas Garnier <thgarnie@google.com>,
	n-horiguchi@ah.jp.nec.com
Subject: Re: [PATCH v5 4/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions
Date: Tue, 18 Jul 2017 07:51:28 +0800	[thread overview]
Message-ID: <20170717235128.GB2344@x1> (raw)
In-Reply-To: <CAGXu5jL5EVDt4AULM_N+vh-5gG_gmtsKcxFwWpSEx5pq7OgPvA@mail.gmail.com>

On 07/17/17 at 04:13pm, Kees Cook wrote:
> > +#ifdef CONFIG_EFI
> > +/*
> > + * Returns true if mirror region found (and must have been processed
> > + * for slots adding)
> > + */
> > +static bool process_efi_entries(unsigned long minimum,
> > +                               unsigned long image_size)
> > +{
> > +       struct efi_info *e = &boot_params->efi_info;
> > +       bool efi_mirror_found = false;
> > +       struct mem_vector region;
> > +       efi_memory_desc_t *md;
> > +       unsigned long pmap;
> > +       char *signature;
> > +       u32 nr_desc;
> > +       int i;
> > +
> > +       signature = (char *)&boot_params->efi_info.efi_loader_signature;
> > +       if (strncmp(signature, EFI32_LOADER_SIGNATURE, 4) &&
> > +           strncmp(signature, EFI64_LOADER_SIGNATURE, 4))
> > +               return false;
> > +
> > +#ifdef CONFIG_X86_32
> > +       /* Can't handle data above 4GB at this time */
> > +       if (e->efi_memmap_hi) {
> > +               warn("Memory map is above 4GB, EFI should be disabled.\n");
> > +               return false;
> > +       }
> > +       pmap =  e->efi_memmap;
> > +#else
> > +       pmap = (e->efi_memmap | ((__u64)e->efi_memmap_hi << 32));
> > +#endif
> > +
> > +       nr_desc = e->efi_memmap_size / e->efi_memdesc_size;
> > +       for (i = 0; i < nr_desc; i++) {
> > +               md = (efi_memory_desc_t *)(pmap + (i * e->efi_memdesc_size));
> > +               if (md->attribute & EFI_MEMORY_MORE_RELIABLE) {
> > +                       region.start = md->phys_addr;
> > +                       region.size = md->num_pages << EFI_PAGE_SHIFT;
> > +                       process_mem_region(&region, minimum, image_size);
> > +                       efi_mirror_found = true;
> > +
> > +                       if (slot_area_index == MAX_SLOT_AREA) {
> > +                               debug_putstr("Aborted efi scan (slot_areas full)!\n");
> 
> Should this text be capitalized to "EFI" or expanded to "EFI mirror"?

Yeah, this should be capitalized. And it should be EFI mirror here, just
later Naoya will add other features about EFI, not only EFI mirror. Let
me change it to EFI mirror, and Naoya can rebase on it.

Many thanks for your reviewing, Kees!

> 
> > +                               break;
> > +                       }
> > +               }
> > +       }
> > +
> > +       return efi_mirror_found;
> > +}
> > +#else
> > +static inline bool process_efi_entries(unsigned long minimum,
> > +                                      unsigned long image_size)
> > +{
> > +       return false;
> > +}
> > +#endif
> > +
> >  static void process_e820_entries(unsigned long minimum,
> >                                  unsigned long image_size)
> >  {
> > @@ -586,13 +647,16 @@ static unsigned long find_random_phys_addr(unsigned long minimum,
> >  {
> >         /* Check if we had too many memmaps. */
> >         if (memmap_too_large) {
> > -               debug_putstr("Aborted e820 scan (more than 4 memmap= args)!\n");
> > +               debug_putstr("Aborted memory entries scan (more than 4 memmap= args)!\n");
> >                 return 0;
> >         }
> >
> >         /* Make sure minimum is aligned. */
> >         minimum = ALIGN(minimum, CONFIG_PHYSICAL_ALIGN);
> >
> > +       if(process_efi_entries(minimum, image_size))
> 
> Style nit: space between "if" and "(".

Will change, could I forget running checkpatch script.

> 
> > +               return slots_fetch_random();
> > +
> >         process_e820_entries(minimum, image_size);
> >         return slots_fetch_random();
> >  }
> > @@ -652,7 +716,7 @@ void choose_random_location(unsigned long input,
> >          */
> >         min_addr = min(*output, 512UL << 20);
> >
> > -       /* Walk e820 and find a random address. */
> > +       /* Walk available memory entries to find a random address. */
> >         random_addr = find_random_phys_addr(min_addr, output_size);
> >         if (!random_addr) {
> >                 warn("Physical KASLR disabled: no suitable memory region!");
> > --
> > 2.5.5
> >
> 
> Otherwise, looks fine to me for the KASLR piece; I can't speak
> specifically to the EFI logic. :)
> 
> Reviewed-by: Kees Cook <keescook@chromium.org>

I will repost with the clean up change and adding your Reviewed-by
since no functionality change. Will see if there will be any EFI
related comment.

Thanks again for reviewing and great suggestions!

Thanks
Baoquan

  reply	other threads:[~2017-07-17 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 14:19 [PATCH v5 0/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions Baoquan He
2017-07-13 14:19 ` [PATCH v5 1/4] x86/boot/KASLR: Wrap e820 entries walking code into new function process_e820_entries() Baoquan He
2017-07-13 14:19 ` [PATCH v5 2/4] x86/boot/KASLR: Switch to pass struct mem_vector to process_e820_entry() Baoquan He
2017-07-13 14:19 ` [PATCH v5 3/4] x86/boot/KASLR: Rename process_e820_entry() into process_mem_region() Baoquan He
2017-07-13 14:19 ` [PATCH v5 4/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions Baoquan He
2017-07-17 23:13   ` Kees Cook
2017-07-17 23:51     ` Baoquan He [this message]
2017-07-18 11:18   ` [PATCH v6 " Baoquan He

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=20170717235128.GB2344@x1 \
    --to=bhe@redhat.com \
    --cc=fanc.fnst@cn.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=tglx@linutronix.de \
    --cc=thgarnie@google.com \
    --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