From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Baoquan He <bhe@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
indou.takao@jp.fujitsu.com, caoj.fnst@cn.fujitsu.com
Subject: Re: [PATCH v7 3/3] x86/boot/KASLR: Limit kaslr to choosing the immovable memory
Date: Tue, 25 Sep 2018 09:04:11 +0800 [thread overview]
Message-ID: <20180925010411.GA12561@localhost.localdomain> (raw)
In-Reply-To: <CAGXu5jK13F7EY--zAVWq-=P2-Lt7n-K05ctL-vH7S=rcWKQoOw@mail.gmail.com>
On Sat, Sep 22, 2018 at 08:48:53AM -0700, Kees Cook wrote:
>On Thu, Sep 13, 2018 at 3:46 AM, Chao Fan <fanc.fnst@cn.fujitsu.com> wrote:
>> +#ifdef CONFIG_MEMORY_HOTREMOVE
>> + /*
>> + * If immovable memory found, filter the intersection between
>> + * immovable memory and region to slots_count.
>> + * Otherwise, go on old code.
>> + */
>> + for (i = 0; i < num_immovable_mem; i++) {
>> + struct mem_vector entry;
>> + unsigned long long start, end, entry_end, region_end;
>> +
>> + start = immovable_mem[i].start;
>> + end = start + immovable_mem[i].size;
>> + region_end = region->start + region->size;
>> +
>> + entry.start = clamp(region->start, start, end);
>> + entry_end = clamp(region_end, start, end);
>> +
>> + if (entry.start + image_size < entry_end) {
>
>Can this logic be rewritten to use the existing mem_overlaps() check
>instead? I think that would make it much more readable.
>
Sure, I will reuse mem_overlaps() instead of this logical.
>Otherwise, yes, this all looks fine.
Thank you for the review.
Thanks,
Chao Fan
>
>-Kees
>
>> + entry.size = entry_end - entry.start;
>> + slots_count(&entry, minimum, image_size);
>> +
>> + if (slot_area_index == MAX_SLOT_AREA) {
>> + debug_putstr("Aborted e820/efi memmap scan (slot_areas full)!\n");
>> + return 1;
>> + }
>> + }
>> + }
>> + return 0;
>> +#endif
>> +}
>> +
>> #ifdef CONFIG_EFI
>> /*
>> * Returns true if mirror region found (and must have been processed
>> @@ -720,11 +775,8 @@ process_efi_entries(unsigned long minimum, unsigned long image_size)
>>
>> region.start = md->phys_addr;
>> region.size = md->num_pages << EFI_PAGE_SHIFT;
>> - process_mem_region(®ion, minimum, image_size);
>> - if (slot_area_index == MAX_SLOT_AREA) {
>> - debug_putstr("Aborted EFI scan (slot_areas full)!\n");
>> + if (process_mem_region(®ion, minimum, image_size))
>> break;
>> - }
>> }
>> return true;
>> }
>> @@ -751,11 +803,8 @@ static void process_e820_entries(unsigned long minimum,
>> continue;
>> region.start = entry->addr;
>> region.size = entry->size;
>> - process_mem_region(®ion, minimum, image_size);
>> - if (slot_area_index == MAX_SLOT_AREA) {
>> - debug_putstr("Aborted e820 scan (slot_areas full)!\n");
>> + if (process_mem_region(®ion, minimum, image_size))
>> break;
>> - }
>> }
>> }
>>
>> --
>> 2.17.1
>>
>>
>>
>
>
>
>--
>Kees Cook
>Pixel Security
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Baoquan He <bhe@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
<indou.takao@jp.fujitsu.com>, <caoj.fnst@cn.fujitsu.com>
Subject: Re: [PATCH v7 3/3] x86/boot/KASLR: Limit kaslr to choosing the immovable memory
Date: Tue, 25 Sep 2018 09:04:11 +0800 [thread overview]
Message-ID: <20180925010411.GA12561@localhost.localdomain> (raw)
In-Reply-To: <CAGXu5jK13F7EY--zAVWq-=P2-Lt7n-K05ctL-vH7S=rcWKQoOw@mail.gmail.com>
On Sat, Sep 22, 2018 at 08:48:53AM -0700, Kees Cook wrote:
>On Thu, Sep 13, 2018 at 3:46 AM, Chao Fan <fanc.fnst@cn.fujitsu.com> wrote:
>> +#ifdef CONFIG_MEMORY_HOTREMOVE
>> + /*
>> + * If immovable memory found, filter the intersection between
>> + * immovable memory and region to slots_count.
>> + * Otherwise, go on old code.
>> + */
>> + for (i = 0; i < num_immovable_mem; i++) {
>> + struct mem_vector entry;
>> + unsigned long long start, end, entry_end, region_end;
>> +
>> + start = immovable_mem[i].start;
>> + end = start + immovable_mem[i].size;
>> + region_end = region->start + region->size;
>> +
>> + entry.start = clamp(region->start, start, end);
>> + entry_end = clamp(region_end, start, end);
>> +
>> + if (entry.start + image_size < entry_end) {
>
>Can this logic be rewritten to use the existing mem_overlaps() check
>instead? I think that would make it much more readable.
>
Sure, I will reuse mem_overlaps() instead of this logical.
>Otherwise, yes, this all looks fine.
Thank you for the review.
Thanks,
Chao Fan
>
>-Kees
>
>> + entry.size = entry_end - entry.start;
>> + slots_count(&entry, minimum, image_size);
>> +
>> + if (slot_area_index == MAX_SLOT_AREA) {
>> + debug_putstr("Aborted e820/efi memmap scan (slot_areas full)!\n");
>> + return 1;
>> + }
>> + }
>> + }
>> + return 0;
>> +#endif
>> +}
>> +
>> #ifdef CONFIG_EFI
>> /*
>> * Returns true if mirror region found (and must have been processed
>> @@ -720,11 +775,8 @@ process_efi_entries(unsigned long minimum, unsigned long image_size)
>>
>> region.start = md->phys_addr;
>> region.size = md->num_pages << EFI_PAGE_SHIFT;
>> - process_mem_region(®ion, minimum, image_size);
>> - if (slot_area_index == MAX_SLOT_AREA) {
>> - debug_putstr("Aborted EFI scan (slot_areas full)!\n");
>> + if (process_mem_region(®ion, minimum, image_size))
>> break;
>> - }
>> }
>> return true;
>> }
>> @@ -751,11 +803,8 @@ static void process_e820_entries(unsigned long minimum,
>> continue;
>> region.start = entry->addr;
>> region.size = entry->size;
>> - process_mem_region(®ion, minimum, image_size);
>> - if (slot_area_index == MAX_SLOT_AREA) {
>> - debug_putstr("Aborted e820 scan (slot_areas full)!\n");
>> + if (process_mem_region(®ion, minimum, image_size))
>> break;
>> - }
>> }
>> }
>>
>> --
>> 2.17.1
>>
>>
>>
>
>
>
>--
>Kees Cook
>Pixel Security
>
>
next prev parent reply other threads:[~2018-09-25 1:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 10:46 [PATCH v7 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Chao Fan
2018-09-13 10:46 ` Chao Fan
2018-09-13 10:46 ` [PATCH v7 1/3] x86/boot: Add acpitb.c to parse acpi tables Chao Fan
2018-09-13 10:46 ` Chao Fan
2018-09-22 15:45 ` Kees Cook
2018-09-25 1:12 ` Chao Fan
2018-09-25 1:12 ` Chao Fan
2018-09-13 10:46 ` [PATCH v7 2/3] x86/boot/KASLR: Walk srat tables to filter immovable memory Chao Fan
2018-09-13 10:46 ` Chao Fan
2018-09-22 15:46 ` Kees Cook
2018-09-13 10:46 ` [PATCH v7 3/3] x86/boot/KASLR: Limit kaslr to choosing the " Chao Fan
2018-09-13 10:46 ` Chao Fan
2018-09-22 15:48 ` Kees Cook
2018-09-25 1:04 ` Chao Fan [this message]
2018-09-25 1:04 ` Chao Fan
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=20180925010411.GA12561@localhost.localdomain \
--to=fanc.fnst@cn.fujitsu.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bhe@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=keescook@chromium.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.