From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,rppt@kernel.org,pasha.tatashin@soleen.com,graf@amazon.com,pratyush@kernel.org,akpm@linux-foundation.org
Subject: + kho-free-already-restored-pages-when-kho_restore_vmalloc-fails.patch added to mm-nonmm-unstable branch
Date: Tue, 18 Nov 2025 14:16:20 -0800 [thread overview]
Message-ID: <20251118221621.B02DBC2BCAF@smtp.kernel.org> (raw)
The patch titled
Subject: kho: free already restored pages when kho_restore_vmalloc() fails
has been added to the -mm mm-nonmm-unstable branch. Its filename is
kho-free-already-restored-pages-when-kho_restore_vmalloc-fails.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/kho-free-already-restored-pages-when-kho_restore_vmalloc-fails.patch
This patch will later appear in the mm-nonmm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Pratyush Yadav <pratyush@kernel.org>
Subject: kho: free already restored pages when kho_restore_vmalloc() fails
Date: Tue, 18 Nov 2025 19:18:10 +0100
When kho_restore_vmalloc() fails, it frees up the pages array, but not the
pages it contains. These are the pages that were successfully restored
using kho_restore_pages(). If the failure happens when restoring the
pages, the ones successfully restored are leaked. If the failure happens
when allocating the vm_area or when mapping the pages, all the pages of
the preserved vmalloc buffer are leaked.
Free all of the successfully restored pages before returning error.
Link: https://lkml.kernel.org/r/20251118181811.47336-1-pratyush@kernel.org
Fixes: a667300bd53f2 ("kho: add support for preserving vmalloc allocations")
Signed-off-by: Pratyush Yadav <pratyush@kernel.org>
Cc: Alexander Graf <graf@amazon.com>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/liveupdate/kexec_handover.c | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
--- a/kernel/liveupdate/kexec_handover.c~kho-free-already-restored-pages-when-kho_restore_vmalloc-fails
+++ a/kernel/liveupdate/kexec_handover.c
@@ -1088,11 +1088,11 @@ void *kho_restore_vmalloc(const struct k
phys_addr_t phys = chunk->phys[i];
if (idx + contig_pages > total_pages)
- goto err_free_pages_array;
+ goto err_free_pages;
page = kho_restore_pages(phys, contig_pages);
if (!page)
- goto err_free_pages_array;
+ goto err_free_pages;
for (int j = 0; j < contig_pages; j++)
pages[idx++] = page;
@@ -1102,20 +1102,20 @@ void *kho_restore_vmalloc(const struct k
page = kho_restore_pages(virt_to_phys(chunk), 1);
if (!page)
- goto err_free_pages_array;
+ goto err_free_pages;
chunk = KHOSER_LOAD_PTR(chunk->hdr.next);
__free_page(page);
}
if (idx != total_pages)
- goto err_free_pages_array;
+ goto err_free_pages;
area = __get_vm_area_node(total_pages * PAGE_SIZE, align, shift,
vm_flags, VMALLOC_START, VMALLOC_END,
NUMA_NO_NODE, GFP_KERNEL,
__builtin_return_address(0));
if (!area)
- goto err_free_pages_array;
+ goto err_free_pages;
addr = (unsigned long)area->addr;
size = get_vm_area_size(area);
@@ -1130,7 +1130,10 @@ void *kho_restore_vmalloc(const struct k
err_free_vm_area:
free_vm_area(area);
-err_free_pages_array:
+err_free_pages:
+ for (int i = 0; i < idx; i++)
+ __free_page(pages[i]);
+
kvfree(pages);
return NULL;
}
_
Patches currently in -mm which might be from pratyush@kernel.org are
maintainers-add-test_kho-to-khos-entry.patch
maintainers-add-myself-as-a-reviewer-for-kho.patch
liveupdate-luo_file-add-private-argument-to-store-runtime-state.patch
kho-free-chunks-using-free_page-instead-of-kfree.patch
kho-free-already-restored-pages-when-kho_restore_vmalloc-fails.patch
reply other threads:[~2025-11-18 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251118221621.B02DBC2BCAF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=mm-commits@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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 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.