From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/efi: handle potential failure to remap memory map
Date: Thu, 15 Jan 2015 11:50:47 -0500 [thread overview]
Message-ID: <1421340647.22837.2.camel@deneb.redhat.com> (raw)
In-Reply-To: <1421323266-30973-1-git-send-email-ard.biesheuvel@linaro.org>
On Thu, 2015-01-15 at 12:01 +0000, Ard Biesheuvel wrote:
> When remapping the UEFI memory map using ioremap_cache(), we
> have to deal with potential failure. Note that, even if the
> common case is for ioremap_cache() to return the existing linear
> mapping of the memory map, we cannot rely on that to be always the
> case, e.g., in the presence of a mem= kernel parameter.
>
> At the same time, remove a stale comment and move the memmap code
> together.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/kernel/efi.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/kernel/efi.c b/arch/arm64/kernel/efi.c
> index a98415b5979c..c9cb0fbe7aa4 100644
> --- a/arch/arm64/kernel/efi.c
> +++ b/arch/arm64/kernel/efi.c
> @@ -229,19 +229,21 @@ static int __init arm64_enable_runtime_services(void)
> return -1;
> }
>
> - mapsize = memmap.map_end - memmap.map;
> -
> if (efi_runtime_disabled()) {
> pr_info("EFI runtime services will be disabled.\n");
> return -1;
> }
>
> pr_info("Remapping and enabling EFI services.\n");
> - /* replace early memmap mapping with permanent mapping */
> +
> + mapsize = memmap.map_end - memmap.map;
> memmap.map = (__force void *)ioremap_cache((phys_addr_t)memmap.phys_map,
> mapsize);
> + if (!memmap.map) {
> + pr_err("Failed to remap EFI memory map\n");
> + return -1;
> + }
> memmap.map_end = memmap.map + mapsize;
> -
> efi.memmap = &memmap;
>
> efi.systab = (__force void *)ioremap_cache(efi_system_table,
Somewhat unrelated but we should unmap memmap.map if the efi.systab
mapping fails.
Acked-by: Mark Salter <msalter@redhat.com>
prev parent reply other threads:[~2015-01-15 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 12:01 [PATCH] arm64/efi: handle potential failure to remap memory map Ard Biesheuvel
2015-01-15 16:40 ` Mark Rutland
2015-01-16 16:23 ` Catalin Marinas
2015-01-15 16:50 ` Mark Salter [this message]
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=1421340647.22837.2.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).