From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: david.edmondson@oracle.com, kwolf@redhat.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-block@nongnu.org
Subject: [PATCH 1/5] block/vdi: When writing new bmap entry fails, don't leak the buffer
Date: Tue, 16 Mar 2021 17:00:03 +0100 [thread overview]
Message-ID: <20210316160007.135459-2-pbonzini@redhat.com> (raw)
In-Reply-To: <20210316160007.135459-1-pbonzini@redhat.com>
From: David Edmondson <david.edmondson@oracle.com>
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.
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Edmondson <david.edmondson@oracle.com>
Message-Id: <20210309144015.557477-2-david.edmondson@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.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.29.2
next prev parent reply other threads:[~2021-03-16 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 16:00 [PATCH v3 0/5] coroutine rwlock downgrade fix, minor VDI changes Paolo Bonzini
2021-03-16 16:00 ` Paolo Bonzini [this message]
2021-03-16 16:00 ` [PATCH 2/5] block/vdi: Don't assume that blocks are larger than VdiHeader Paolo Bonzini
2021-03-16 16:00 ` [PATCH 3/5] coroutine/mutex: Store the coroutine in the CoWaitRecord only once Paolo Bonzini
2021-03-16 16:00 ` [PATCH 4/5] coroutine-lock: reimplement CoRwLock to fix downgrade bug Paolo Bonzini
2021-03-17 10:40 ` David Edmondson
2021-03-17 12:00 ` Paolo Bonzini
2021-03-16 16:00 ` [PATCH 5/5] test-coroutine: Add rwlock downgrade test Paolo Bonzini
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=20210316160007.135459-2-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=kwolf@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 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).