[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RFC PATCH 1/4] block/vdi: When writing new bmap entry fails, don't leak
From: |
David Edmondson |
Subject: |
[RFC PATCH 1/4] block/vdi: When writing new bmap entry fails, don't leak the buffer |
Date: |
Tue, 9 Mar 2021 10:21:54 +0000 |
If a new bitmap entry is allocated, requiring the entire block to be
written, avoiding leaking the buffer allocated for the block should
the write fail.
Signed-off-by: David Edmondson <david.edmondson@oracle.com>
---
block/vdi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/block/vdi.c b/block/vdi.c
index 5627e7d764..2a6dc26124 100644
--- a/block/vdi.c
+++ b/block/vdi.c
@@ -690,6 +690,7 @@ nonallocating_write:
logout("finished data write\n");
if (ret < 0) {
+ g_free(block);
return ret;
}
--
2.30.1
[RFC PATCH 3/4] coroutine/mutex: Store the coroutine in the CoWaitRecord only once, David Edmondson, 2021/03/09