[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161003195131.GK16071@codeblueprint.co.uk>
Date: Mon, 3 Oct 2016 20:51:31 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Yisheng Xie <xieyisheng1@...wei.com>
Cc: will.deacon@....com, mingo@...nel.org, guohanjun@...wei.com,
mark.rutland@....com, catalin.marinas@....com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-efi@...r.kernel.org, ard.biesheuvel@...aro.org
Subject: Re: [PATCH -next v2] arm*/efi: efi_init error handling fix
On Tue, 20 Sep, at 07:39:53PM, Yisheng Xie wrote:
> There's an early memmap leak in efi_init error path, fix it.
>
> Signed-off-by: Yisheng Xie <xieyisheng1@...wei.com>
> ---
> drivers/firmware/efi/arm-init.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/efi/arm-init.c b/drivers/firmware/efi/arm-init.c
> index 9f8d996..7c2fe57 100644
> --- a/drivers/firmware/efi/arm-init.c
> +++ b/drivers/firmware/efi/arm-init.c
> @@ -245,8 +245,10 @@ void __init efi_init(void)
> "Unexpected EFI_MEMORY_DESCRIPTOR version %ld",
> efi.memmap.desc_version);
>
> - if (uefi_init() < 0)
> + if (uefi_init() < 0) {
> + efi_memmap_unmap();
> return;
> + }
>
> reserve_regions();
> efi_memattr_init();
Thanks, applied to 'next'.
Powered by blists - more mailing lists