From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "qemu-devel" <qemu-devel@nongnu.org>
Cc: "kvm" <kvm@vger.kernel.org>, "Kevin Wolf" <kwolf@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [PATCH] qcow2: fix double-free of Qcow2DiscardRegion in qcow2_process_discards
Date: Sat, 11 Oct 2014 15:14:25 +0800 [thread overview]
Message-ID: <201410111514227991260@sangfor.com> (raw)
In qcow2_update_snapshot_refcount -> qcow2_process_discards() -> bdrv_discard()
may free the Qcow2DiscardRegion which is referenced by "next" pointer in
qcow2_process_discards() now, in next iteration, d = next, so g_free(d)
will double-free this Qcow2DiscardRegion.
qcow2_snapshot_delete
|- qcow2_update_snapshot_refcount
|-- qcow2_process_discards
|--- bdrv_discard
|---- aio_poll
|----- aio_dispatch
|------ bdrv_co_io_em_complete
|------- qemu_coroutine_enter(co->coroutine, NULL); <=== coroutine entry is bdrv_co_do_rw
|--- g_free(d) <== free first Qcow2DiscardRegion is okay
|--- d = next; <== this set is done in QTAILQ_FOREACH_SAFE() macro.
|--- g_free(d); <== double-free will happen if during previous iteration, bdrv_discard had free this object.
bdrv_co_do_rw
|- bdrv_co_do_writev
|-- bdrv_co_do_pwritev
|--- bdrv_aligned_pwritev
|---- qcow2_co_writev
|----- qcow2_alloc_cluster_link_l2
|------ qcow2_free_any_clusters
|------- qcow2_free_clusters
|-------- update_refcount
|--------- qcow2_process_discards
|---------- g_free(d) <== In next iteration, this Qcow2DiscardRegion will be double-free.
Signed-off-by: Zhang Haoyu <zhanghy@sangfor.com>
Signed-off-by: Fu Xuewei <fxw@sangfor.com>
---
block/qcow2-refcount.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
index 2bcaaf9..3b759a3 100644
--- a/block/qcow2-refcount.c
+++ b/block/qcow2-refcount.c
@@ -462,9 +462,9 @@ fail_block:
void qcow2_process_discards(BlockDriverState *bs, int ret)
{
BDRVQcowState *s = bs->opaque;
- Qcow2DiscardRegion *d, *next;
+ Qcow2DiscardRegion *d;
- QTAILQ_FOREACH_SAFE(d, &s->discards, next, next) {
+ while ((d = QTAILQ_FIRST(&s->discards)) != NULL) {
QTAILQ_REMOVE(&s->discards, d, next);
/* Discard is optional, ignore the return value */
--
1.7.12.4
WARNING: multiple messages have this Message-ID (diff)
From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] [PATCH] qcow2: fix double-free of Qcow2DiscardRegion in qcow2_process_discards
Date: Sat, 11 Oct 2014 15:14:25 +0800 [thread overview]
Message-ID: <201410111514227991260@sangfor.com> (raw)
In qcow2_update_snapshot_refcount -> qcow2_process_discards() -> bdrv_discard()
may free the Qcow2DiscardRegion which is referenced by "next" pointer in
qcow2_process_discards() now, in next iteration, d = next, so g_free(d)
will double-free this Qcow2DiscardRegion.
qcow2_snapshot_delete
|- qcow2_update_snapshot_refcount
|-- qcow2_process_discards
|--- bdrv_discard
|---- aio_poll
|----- aio_dispatch
|------ bdrv_co_io_em_complete
|------- qemu_coroutine_enter(co->coroutine, NULL); <=== coroutine entry is bdrv_co_do_rw
|--- g_free(d) <== free first Qcow2DiscardRegion is okay
|--- d = next; <== this set is done in QTAILQ_FOREACH_SAFE() macro.
|--- g_free(d); <== double-free will happen if during previous iteration, bdrv_discard had free this object.
bdrv_co_do_rw
|- bdrv_co_do_writev
|-- bdrv_co_do_pwritev
|--- bdrv_aligned_pwritev
|---- qcow2_co_writev
|----- qcow2_alloc_cluster_link_l2
|------ qcow2_free_any_clusters
|------- qcow2_free_clusters
|-------- update_refcount
|--------- qcow2_process_discards
|---------- g_free(d) <== In next iteration, this Qcow2DiscardRegion will be double-free.
Signed-off-by: Zhang Haoyu <zhanghy@sangfor.com>
Signed-off-by: Fu Xuewei <fxw@sangfor.com>
---
block/qcow2-refcount.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
index 2bcaaf9..3b759a3 100644
--- a/block/qcow2-refcount.c
+++ b/block/qcow2-refcount.c
@@ -462,9 +462,9 @@ fail_block:
void qcow2_process_discards(BlockDriverState *bs, int ret)
{
BDRVQcowState *s = bs->opaque;
- Qcow2DiscardRegion *d, *next;
+ Qcow2DiscardRegion *d;
- QTAILQ_FOREACH_SAFE(d, &s->discards, next, next) {
+ while ((d = QTAILQ_FIRST(&s->discards)) != NULL) {
QTAILQ_REMOVE(&s->discards, d, next);
/* Discard is optional, ignore the return value */
--
1.7.12.4
next reply other threads:[~2014-10-11 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 7:14 Zhang Haoyu [this message]
2014-10-11 7:14 ` [Qemu-devel] [PATCH] qcow2: fix double-free of Qcow2DiscardRegion in qcow2_process_discards Zhang Haoyu
2014-10-12 7:34 ` Kevin Wolf
2014-10-12 7:34 ` [Qemu-devel] " Kevin Wolf
2014-10-12 8:22 ` Zhang Haoyu
2014-10-12 8:22 ` Zhang Haoyu
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=201410111514227991260@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.