From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Ard Biesheuvel <ardb@kernel.org>, <linux-efi@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <mawupeng1@huawei.com>,
<linux-mm@kvack.org>
Subject: Re: [PATCH] efi: stub: prefer mirrored memory for randomized allocations
Date: Thu, 5 May 2022 21:43:26 +0800 [thread overview]
Message-ID: <9472d1d5-7f03-eaaf-2846-a4340163d5c0@huawei.com> (raw)
In-Reply-To: <20220503152131.263711-1-ardb@kernel.org>
On 2022/5/3 23:21, Ard Biesheuvel wrote:
> If the system exposes memory regions with the EFI_MORE_RELIABLE
> attribute, it is implied that it is intended to be used for allocations
> that are relatively important, such as the kernel's static image.
>
> Since efi_random_alloc() is mostly (only) used for allocating space for
> the kernel image, let's update it to take this into account, and
> disregard all memory without the EFI_MORE_RELIABLE attribute if there is
> sufficient memory available that does have this attribute.
>
> Note that this change only affects booting with randomization enabled.
> In other cases, the EFI stub runs the kernel image in place unless its
> placement is unsuitable for some reason (i.e., misaligned, or its BSS
> overlaps with another allocation), and it is left to the bootloader to
> ensure that the kernel was loaded into EFI_MORE_RELIABLE memory if this
> is desired.
>
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> drivers/firmware/efi/libstub/randomalloc.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/firmware/efi/libstub/randomalloc.c b/drivers/firmware/efi/libstub/randomalloc.c
> index 724155b9e10d..07a762910312 100644
> --- a/drivers/firmware/efi/libstub/randomalloc.c
> +++ b/drivers/firmware/efi/libstub/randomalloc.c
> @@ -56,6 +56,7 @@ efi_status_t efi_random_alloc(unsigned long size,
> unsigned long random_seed)
> {
> unsigned long map_size, desc_size, total_slots = 0, target_slot;
> + unsigned long total_mirrored_slots = 0;
> unsigned long buff_size;
> efi_status_t status;
> efi_memory_desc_t *memory_map;
> @@ -86,8 +87,14 @@ efi_status_t efi_random_alloc(unsigned long size,
> slots = get_entry_num_slots(md, size, ilog2(align));
> MD_NUM_SLOTS(md) = slots;
> total_slots += slots;
> + if (md->attribute & EFI_MEMORY_MORE_RELIABLE)
> + total_mirrored_slots += slots;
> }
>
> + /* only consider mirrored slots for randomization if any exist */
> + if (total_mirrored_slots > 0)
> + total_slots = total_mirrored_slots;
> +
The kernel will check 4G lower limit to enable kernelcore=mirror feature.
Do we need some fallback mechanism in case of small mirror slots which
leads to fail allocation for Image?
> /* find a random number between 0 and total_slots */
> target_slot = (total_slots * (u64)(random_seed & U32_MAX)) >> 32;
>
> @@ -107,6 +114,10 @@ efi_status_t efi_random_alloc(unsigned long size,
> efi_physical_addr_t target;
> unsigned long pages;
>
> + if (total_mirrored_slots > 0 &&
> + !(md->attribute & EFI_MEMORY_MORE_RELIABLE))
> + continue;
> +
> if (target_slot >= MD_NUM_SLOTS(md)) {
> target_slot -= MD_NUM_SLOTS(md);
> continue;
next prev parent reply other threads:[~2022-05-05 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:21 Ard Biesheuvel
2022-05-05 13:43 ` Kefeng Wang [this message]
2022-05-05 16:12 ` Ard Biesheuvel
2022-05-06 1:42 ` Kefeng Wang
2022-05-06 6:19 ` Ard Biesheuvel
2022-05-06 1:06 ` Kefeng Wang
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=9472d1d5-7f03-eaaf-2846-a4340163d5c0@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawupeng1@huawei.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