* [PATCH] hw/nvme: Fix memory leak in nvme_dsm
@ 2024-07-02 23:13 Zheyu Ma
2024-07-03 0:28 ` Xingtao Yao (Fujitsu) via
2024-07-10 7:37 ` Klaus Jensen
0 siblings, 2 replies; 3+ messages in thread
From: Zheyu Ma @ 2024-07-02 23:13 UTC (permalink / raw)
To: Keith Busch, Klaus Jensen, Jesper Devantier
Cc: Zheyu Ma, qemu-block, qemu-devel
The allocated memory to hold LBA ranges leaks in the nvme_dsm function. This
happens because the allocated memory for iocb->range is not freed in all
error handling paths.
Fix this by adding a free to ensure that the allocated memory is properly freed.
ASAN log:
==3075137==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 480 byte(s) in 6 object(s) allocated from:
#0 0x55f1f8a0eddd in malloc llvm/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3
#1 0x7f531e0f6738 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5e738)
#2 0x55f1faf1f091 in blk_aio_get block/block-backend.c:2583:12
#3 0x55f1f945c74b in nvme_dsm hw/nvme/ctrl.c:2609:30
#4 0x55f1f945831b in nvme_io_cmd hw/nvme/ctrl.c:4470:16
#5 0x55f1f94561b7 in nvme_process_sq hw/nvme/ctrl.c:7039:29
Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
---
hw/nvme/ctrl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/nvme/ctrl.c b/hw/nvme/ctrl.c
index 127c3d2383..cf610eab21 100644
--- a/hw/nvme/ctrl.c
+++ b/hw/nvme/ctrl.c
@@ -2592,6 +2592,7 @@ next:
done:
iocb->aiocb = NULL;
iocb->common.cb(iocb->common.opaque, iocb->ret);
+ g_free(iocb->range);
qemu_aio_unref(iocb);
}
--
2.34.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* RE: [PATCH] hw/nvme: Fix memory leak in nvme_dsm
2024-07-02 23:13 [PATCH] hw/nvme: Fix memory leak in nvme_dsm Zheyu Ma
@ 2024-07-03 0:28 ` Xingtao Yao (Fujitsu) via
2024-07-10 7:37 ` Klaus Jensen
1 sibling, 0 replies; 3+ messages in thread
From: Xingtao Yao (Fujitsu) via @ 2024-07-03 0:28 UTC (permalink / raw)
To: Zheyu Ma, Keith Busch, Klaus Jensen, Jesper Devantier
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
> -----Original Message-----
> From: qemu-devel-bounces+yaoxt.fnst=fujitsu.com@nongnu.org
> <qemu-devel-bounces+yaoxt.fnst=fujitsu.com@nongnu.org> On Behalf Of Zheyu
> Ma
> Sent: Wednesday, July 3, 2024 7:13 AM
> To: Keith Busch <kbusch@kernel.org>; Klaus Jensen <its@irrelevant.dk>; Jesper
> Devantier <foss@defmacro.it>
> Cc: Zheyu Ma <zheyuma97@gmail.com>; qemu-block@nongnu.org;
> qemu-devel@nongnu.org
> Subject: [PATCH] hw/nvme: Fix memory leak in nvme_dsm
>
> The allocated memory to hold LBA ranges leaks in the nvme_dsm function. This
> happens because the allocated memory for iocb->range is not freed in all
> error handling paths.
>
> Fix this by adding a free to ensure that the allocated memory is properly freed.
>
> ASAN log:
> ==3075137==ERROR: LeakSanitizer: detected memory leaks
>
> Direct leak of 480 byte(s) in 6 object(s) allocated from:
> #0 0x55f1f8a0eddd in malloc
> llvm/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3
> #1 0x7f531e0f6738 in g_malloc
> (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5e738)
> #2 0x55f1faf1f091 in blk_aio_get block/block-backend.c:2583:12
> #3 0x55f1f945c74b in nvme_dsm hw/nvme/ctrl.c:2609:30
> #4 0x55f1f945831b in nvme_io_cmd hw/nvme/ctrl.c:4470:16
> #5 0x55f1f94561b7 in nvme_process_sq hw/nvme/ctrl.c:7039:29
>
> Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
> ---
> hw/nvme/ctrl.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/nvme/ctrl.c b/hw/nvme/ctrl.c
> index 127c3d2383..cf610eab21 100644
> --- a/hw/nvme/ctrl.c
> +++ b/hw/nvme/ctrl.c
> @@ -2592,6 +2592,7 @@ next:
> done:
> iocb->aiocb = NULL;
> iocb->common.cb(iocb->common.opaque, iocb->ret);
> + g_free(iocb->range);
> qemu_aio_unref(iocb);
> }
>
> --
> 2.34.1
>
Reviewed-by: Xingtao Yao <yaoxt.fnst@fujitsu.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] hw/nvme: Fix memory leak in nvme_dsm
2024-07-02 23:13 [PATCH] hw/nvme: Fix memory leak in nvme_dsm Zheyu Ma
2024-07-03 0:28 ` Xingtao Yao (Fujitsu) via
@ 2024-07-10 7:37 ` Klaus Jensen
1 sibling, 0 replies; 3+ messages in thread
From: Klaus Jensen @ 2024-07-10 7:37 UTC (permalink / raw)
To: Zheyu Ma; +Cc: Keith Busch, Jesper Devantier, qemu-block, qemu-devel
[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]
On Jul 3 01:13, Zheyu Ma wrote:
> The allocated memory to hold LBA ranges leaks in the nvme_dsm function. This
> happens because the allocated memory for iocb->range is not freed in all
> error handling paths.
>
> Fix this by adding a free to ensure that the allocated memory is properly freed.
>
> ASAN log:
> ==3075137==ERROR: LeakSanitizer: detected memory leaks
>
> Direct leak of 480 byte(s) in 6 object(s) allocated from:
> #0 0x55f1f8a0eddd in malloc llvm/compiler-rt/lib/asan/asan_malloc_linux.cpp:129:3
> #1 0x7f531e0f6738 in g_malloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5e738)
> #2 0x55f1faf1f091 in blk_aio_get block/block-backend.c:2583:12
> #3 0x55f1f945c74b in nvme_dsm hw/nvme/ctrl.c:2609:30
> #4 0x55f1f945831b in nvme_io_cmd hw/nvme/ctrl.c:4470:16
> #5 0x55f1f94561b7 in nvme_process_sq hw/nvme/ctrl.c:7039:29
>
> Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
> ---
> hw/nvme/ctrl.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/nvme/ctrl.c b/hw/nvme/ctrl.c
> index 127c3d2383..cf610eab21 100644
> --- a/hw/nvme/ctrl.c
> +++ b/hw/nvme/ctrl.c
> @@ -2592,6 +2592,7 @@ next:
> done:
> iocb->aiocb = NULL;
> iocb->common.cb(iocb->common.opaque, iocb->ret);
> + g_free(iocb->range);
> qemu_aio_unref(iocb);
> }
>
> --
> 2.34.1
>
Thanks! LGTM
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
Fixes: d7d1474fd85d ("hw/nvme: reimplement dsm to allow cancellation")
Cc: qemu-stable@nongnu.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-07-10 7:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-02 23:13 [PATCH] hw/nvme: Fix memory leak in nvme_dsm Zheyu Ma
2024-07-03 0:28 ` Xingtao Yao (Fujitsu) via
2024-07-10 7:37 ` Klaus Jensen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).