From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/4] efi_loader: check alignment in efi_add_memory_map()
Date: Thu, 14 May 2020 20:35:15 +0200 [thread overview]
Message-ID: <8c868d16-402b-d010-3e67-4cc620e3e127@gmx.de> (raw)
In-Reply-To: <20200514123831.30157-3-michael@walle.cc>
On 5/14/20 2:38 PM, Michael Walle wrote:
> The first argument has to be aligned with EFI_PAGE_SIZE. This alignment
> is already checked for external callers but it is not checked for
> internal callers. Unfortunately, most of the time the return value is
> not checked, so scream loud and clear.
Why do you mention the return value here?
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> lib/efi_loader/efi_memory.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/lib/efi_loader/efi_memory.c b/lib/efi_loader/efi_memory.c
> index fd79178da9..b56e19cb30 100644
> --- a/lib/efi_loader/efi_memory.c
> +++ b/lib/efi_loader/efi_memory.c
> @@ -248,6 +248,9 @@ efi_status_t efi_add_memory_map(uint64_t start, uint64_t pages, int memory_type,
> EFI_PRINT("%s: 0x%llx 0x%llx %d %s\n", __func__,
> start, pages, memory_type, overlap_only_ram ? "yes" : "no");
>
> + if (start & EFI_PAGE_MASK)
> + panic("%s: start not aligned\n", __func__);
> +
Did you find any internal caller that has a problem?
We do not want to increase code size.
Best regards
Heinrich
> if (memory_type >= EFI_MAX_MEMORY_TYPE)
> return EFI_INVALID_PARAMETER;
>
>
next prev parent reply other threads:[~2020-05-14 18:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:38 [PATCH 0/4] bootefi fixes for aarch64/layerscape Michael Walle
2020-05-14 12:38 ` [PATCH 1/4] efi_loader: aarch64: align runtime section to 64kb Michael Walle
2020-05-14 18:27 ` Heinrich Schuchardt
2020-05-14 19:04 ` Michael Walle
2020-05-14 21:03 ` Heinrich Schuchardt
2020-05-14 22:02 ` Michael Walle
2020-05-14 22:27 ` Heinrich Schuchardt
2020-05-14 23:04 ` Heinrich Schuchardt
2020-05-15 11:39 ` Michael Walle
2020-05-28 17:11 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 2/4] efi_loader: check alignment in efi_add_memory_map() Michael Walle
2020-05-14 18:35 ` Heinrich Schuchardt [this message]
2020-05-14 18:50 ` Michael Walle
2020-05-14 22:02 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 3/4] fsl-layerscape: align first parameter of efi_add_memory_map() Michael Walle
2020-05-14 18:39 ` Heinrich Schuchardt
2020-05-14 12:38 ` [PATCH 4/4] efi_loader: call smp_kick_all_cpus() Michael Walle
2020-05-14 18:46 ` Heinrich Schuchardt
2020-05-14 20:17 ` Alexander Graf
2020-05-14 20:35 ` Michael Walle
2020-05-16 15:54 ` Michael Walle
2020-05-18 18:30 ` Tom Rini
2020-05-18 18:45 ` Heinrich Schuchardt
2020-05-18 19:23 ` Tom Rini
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=8c868d16-402b-d010-3e67-4cc620e3e127@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=u-boot@lists.denx.de \
/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.