Re: [PATCH v2 0/9] memblock: improve late freeing of reserved memory
Mike Rapoport <[email protected]>
| Newsgroups | org.kernel.vger.sparclinux,dev.linux.lists.iommu,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-efi,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-trace-kernel,org.kvack.linux-mm,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <177442863989.343689.8532363597437067519.b4-ty@b4> |
On Mon, 23 Mar 2026 09:48:27 +0200, Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" <[email protected]> > > Hi, > > Following a recent discussion about leaks in x86 EFI [1], I audited usage of > memblock_free_late() and free_reserved_area() and made some imporovements how > we handle late freeing of the memory allocated with memblock. > > [...] Applied to for-next branch of memblock.git tree, thanks! [1/9] memblock: reserve_mem: fix end caclulation in reserve_mem_release_by_name() commit: ea459d3c24fefd90b60a702f4a73833434ae0248 [2/9] powerpc: fadump: pair alloc_pages_exact() with free_pages_exact() commit: 6e827110aea5fb9c53a5bf070413ffe5cad105b0 [3/9] powerpc: opal-core: pair alloc_pages_exact() with free_pages_exact() commit: 3cf80188ecb828ed034ba562614cf1d48156b126 [4/9] mm: move free_reserved_area() to mm/memblock.c commit: 0aa264cda784f9fbe1a80ef13144cf81610086c7 [5/9] memblock: make free_reserved_area() more robust commit: 456ac994018598bc57ceaacb8a2c72e722c9755b [6/9] memblock: extract page freeing from free_reserved_area() into a helper commit: 40191dae9ed84c816b593bb1b36a80f86c2279d1 [7/9] memblock: make free_reserved_area() update memblock if ARCH_KEEP_MEMBLOCK=y commit: b9e028ca869de24df00206d7ec640380670fc38f [8/9] memblock, treewide: make memblock_free() handle late freeing commit: 64cb853c2ab4d8bd25b965f05e33ac0c6672bae7 [9/9] memblock: warn when freeing reserved memory before memory map is initialized commit: c7fc9cde41be029cf6675befbafcbb2dab40b39b tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock branch: for-next -- Sincerely yours, Mike.