From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH 1/4] qcow2: Drop unused cluster_data
Date: Mon, 2 Jul 2018 10:58:33 +0800 [thread overview]
Message-ID: <20180702025836.20957-2-famz@redhat.com> (raw)
In-Reply-To: <20180702025836.20957-1-famz@redhat.com>
Reported-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
---
block/qcow2.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
index 2f9e58e0c4..3177c72de0 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -3338,7 +3338,6 @@ qcow2_co_copy_range_to(BlockDriverState *bs,
int ret;
unsigned int cur_bytes; /* number of sectors in current iteration */
uint64_t cluster_offset;
- uint8_t *cluster_data = NULL;
QCowL2Meta *l2meta = NULL;
assert(!bs->encrypted);
@@ -3397,7 +3396,6 @@ fail:
qemu_co_mutex_unlock(&s->lock);
- qemu_vfree(cluster_data);
trace_qcow2_writev_done_req(qemu_coroutine_self(), ret);
return ret;
--
2.17.1
next prev parent reply other threads:[~2018-07-02 2:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 2:58 [Qemu-devel] [PATCH 0/4] block: Trivial fixes in offloading code Fam Zheng
2018-07-02 2:58 ` Fam Zheng [this message]
2018-07-02 2:58 ` [Qemu-devel] [PATCH 2/4] file-posix: Fix fd_open check in raw_co_copy_range_to Fam Zheng
2018-07-02 2:58 ` [Qemu-devel] [PATCH 3/4] qcow2: Drop unreachable break Fam Zheng
2018-07-02 2:58 ` [Qemu-devel] [PATCH 4/4] raw: Drop superfluous semicolon Fam Zheng
2018-07-02 12:35 ` [Qemu-devel] [PATCH 0/4] block: Trivial fixes in offloading code Max Reitz
2018-07-03 1:26 ` Fam Zheng
2018-07-04 14:09 ` Max Reitz
2018-07-02 15:19 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20180702025836.20957-2-famz@redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).