From: Borislav Petkov <bp@alien8.de>
To: Ard Biesheuvel <ardb+git@google.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Ashish Kalra <Ashish.Kalra@amd.com>,
Dave Young <dyoung@redhat.com>, Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH] x86/efi: Free EFI memory map only when installing a new one.
Date: Mon, 10 Jun 2024 16:11:56 +0200 [thread overview]
Message-ID: <20240610141156.GDZmcJrEi11xESpy3a@fat_crate.local> (raw)
In-Reply-To: <20240610140932.2489527-2-ardb+git@google.com>
+ Dan because of
f0ef6523475f ("efi: Fix efi_memmap_alloc() leaks")
Thanks Ard.
On Mon, Jun 10, 2024 at 04:09:33PM +0200, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> The logic in __efi_memmap_init() is shared between two different
> execution flows:
> - mapping the EFI memory map early or late into the kernel VA space, so
> that its entries can be accessed;
> - cloning the EFI memory map in order to insert new entries that are
> created as a result of creating a memory reservation
> (efi_arch_mem_reserve())
>
> In the former case, the underlying memory containing the kernel's view
> of the EFI memory map (which may be heavily modified by the kernel
> itself on x86) is not modified at all, and the only thing that changes
> is the virtual mapping of this memory, which is different between early
> and late boot.
>
> In the latter case, an entirely new allocation is created that carries a
> new, updated version of the kernel's view of the EFI memory map. When
> installing this new version, the old version will no longer be
> referenced, and if the memory was allocated by the kernel, it will leak
> unless it gets freed.
>
> The logic that implements this freeing currently lives on the code path
> that is shared between these two use cases, but it should only apply to
> the latter. So move it to the correct spot.
>
> Cc: Ashish Kalra <Ashish.Kalra@amd.com>
> Cc: Dave Young <dyoung@redhat.com>
> Cc: Mike Rapoport <rppt@kernel.org>
> Cc: Borislav Petkov <bp@alien8.de>
> Link: https://lore.kernel.org/all/36ad5079-4326-45ed-85f6-928ff76483d3@amd.com
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> arch/x86/platform/efi/memmap.c | 5 +++++
> drivers/firmware/efi/memmap.c | 5 -----
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/x86/platform/efi/memmap.c b/arch/x86/platform/efi/memmap.c
> index 4ef20b49eb5e..4990244e5168 100644
> --- a/arch/x86/platform/efi/memmap.c
> +++ b/arch/x86/platform/efi/memmap.c
> @@ -97,6 +97,11 @@ int __init efi_memmap_install(struct efi_memory_map_data *data)
> if (efi_enabled(EFI_PARAVIRT))
> return 0;
>
> + if (efi.memmap.flags & (EFI_MEMMAP_MEMBLOCK | EFI_MEMMAP_SLAB))
> + __efi_memmap_free(efi.memmap.phys_map,
> + efi.memmap.desc_size * efi.memmap.nr_map,
> + efi.memmap.flags);
> +
> return __efi_memmap_init(data);
> }
>
> diff --git a/drivers/firmware/efi/memmap.c b/drivers/firmware/efi/memmap.c
> index 3365944f7965..3759e95a7407 100644
> --- a/drivers/firmware/efi/memmap.c
> +++ b/drivers/firmware/efi/memmap.c
> @@ -51,11 +51,6 @@ int __init __efi_memmap_init(struct efi_memory_map_data *data)
> return -ENOMEM;
> }
>
> - if (efi.memmap.flags & (EFI_MEMMAP_MEMBLOCK | EFI_MEMMAP_SLAB))
> - __efi_memmap_free(efi.memmap.phys_map,
> - efi.memmap.desc_size * efi.memmap.nr_map,
> - efi.memmap.flags);
> -
> map.phys_map = data->phys_map;
> map.nr_map = data->size / data->desc_size;
> map.map_end = map.map + data->size;
> --
> 2.45.2.505.gda0bf45e8d-goog
>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-06-10 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 14:09 [PATCH] x86/efi: Free EFI memory map only when installing a new one Ard Biesheuvel
2024-06-10 14:11 ` Borislav Petkov [this message]
2024-06-12 10:36 ` Dave Young
2024-06-12 12:29 ` Ard Biesheuvel
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=20240610141156.GDZmcJrEi11xESpy3a@fat_crate.local \
--to=bp@alien8.de \
--cc=Ashish.Kalra@amd.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dyoung@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox