* [PATCH] kho: test: clean up residual memory upon test_kho module unload
@ 2026-01-07 2:24 l00580197
2026-01-07 10:06 ` Mike Rapoport
0 siblings, 1 reply; 2+ messages in thread
From: l00580197 @ 2026-01-07 2:24 UTC (permalink / raw)
To: Alexander Graf, Mike Rapoport, Pasha Tatashin
Cc: Pratyush Yadav, kexec, linux-mm, linux-kernel, hewenliang4, Long Wei
From: Long Wei <longwei27@huawei.com>
During the initialization phase, the test_kho module invokes the
kho_preserve_folio function, which internally configures bitmaps
within kho_mem_track and establishes chunk linked lists in KHO.
Upon unloading the test_kho module, it is necessary to clean up
these states.
Signed-off-by: Long Wei <longwei27@huawei.com>
---
lib/test_kho.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/lib/test_kho.c b/lib/test_kho.c
index 47de56280795..69230da5a056 100644
--- a/lib/test_kho.c
+++ b/lib/test_kho.c
@@ -339,11 +339,15 @@ module_init(kho_test_init);
static void kho_test_cleanup(void)
{
+ /* unpreserve and free the data stored in folios */
+ kho_test_unpreserve_data(&kho_test_state);
for (int i = 0; i < kho_test_state.nr_folios; i++)
folio_put(kho_test_state.folios[i]);
kvfree(kho_test_state.folios);
- vfree(kho_test_state.folios_info);
+
+ /* Unpreserve and release the FDT folio */
+ kho_unpreserve_folio(kho_test_state.fdt);
folio_put(kho_test_state.fdt);
}
--
2.43.0
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] kho: test: clean up residual memory upon test_kho module unload
2026-01-07 2:24 [PATCH] kho: test: clean up residual memory upon test_kho module unload l00580197
@ 2026-01-07 10:06 ` Mike Rapoport
0 siblings, 0 replies; 2+ messages in thread
From: Mike Rapoport @ 2026-01-07 10:06 UTC (permalink / raw)
To: l00580197
Cc: Alexander Graf, Pasha Tatashin, Pratyush Yadav, kexec, linux-mm,
linux-kernel, hewenliang4
On Wed, Jan 07, 2026 at 10:24:27AM +0800, l00580197 wrote:
> From: Long Wei <longwei27@huawei.com>
>
> During the initialization phase, the test_kho module invokes the
> kho_preserve_folio function, which internally configures bitmaps
> within kho_mem_track and establishes chunk linked lists in KHO.
> Upon unloading the test_kho module, it is necessary to clean up
> these states.
>
> Signed-off-by: Long Wei <longwei27@huawei.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> lib/test_kho.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/lib/test_kho.c b/lib/test_kho.c
> index 47de56280795..69230da5a056 100644
> --- a/lib/test_kho.c
> +++ b/lib/test_kho.c
> @@ -339,11 +339,15 @@ module_init(kho_test_init);
>
> static void kho_test_cleanup(void)
> {
> + /* unpreserve and free the data stored in folios */
> + kho_test_unpreserve_data(&kho_test_state);
> for (int i = 0; i < kho_test_state.nr_folios; i++)
> folio_put(kho_test_state.folios[i]);
>
> kvfree(kho_test_state.folios);
> - vfree(kho_test_state.folios_info);
> +
> + /* Unpreserve and release the FDT folio */
> + kho_unpreserve_folio(kho_test_state.fdt);
> folio_put(kho_test_state.fdt);
> }
>
> --
> 2.43.0
>
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-01-07 10:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-01-07 2:24 [PATCH] kho: test: clean up residual memory upon test_kho module unload l00580197
2026-01-07 10:06 ` Mike Rapoport
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox