qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v2 1/2] qcow2: Undo leaked allocations in co_writev
Date: Fri, 11 Oct 2013 09:36:25 +0200	[thread overview]
Message-ID: <1381476986-3032-2-git-send-email-mreitz@redhat.com> (raw)
In-Reply-To: <1381476986-3032-1-git-send-email-mreitz@redhat.com>

If the write request spans more than one L2 table,
qcow2_alloc_cluster_offset cannot handle the required allocations
atomically. This results in leaks if it allocated new clusters in any
but the last L2 table touched and an error occurs in qcow2_co_writev
before having established the L2 link. These non-atomic allocations
were, however, indeed successful and are therefore given to the caller
in the L2Meta list.

If an error occurs in qcow2_co_writev and the L2Meta list is unwound,
all its remaining entries are clusters whose L2 links were not yet
established. Thus, all allocations in that list should be undone.

Signed-off-by: Max Reitz <mreitz@redhat.com>
---
 block/qcow2.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/block/qcow2.c b/block/qcow2.c
index 13e34f0..69d8270 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -1078,6 +1078,14 @@ static coroutine_fn int qcow2_co_writev(BlockDriverState *bs,
                 goto fail;
             }
 
+            /* WARNING: If adding a "goto fail" anywhere from here until the
+             * current QCowL2Meta element is removed from the l2meta list (that
+             * is, until the end of this loop), mind the qcow2_free_clusters()
+             * call after the fail label. Always make sure that every list
+             * element with a non-zero nb_clusters value remaining when reaching
+             * the while loop after that label indeed corresponds to a leaked
+             * allocation which has to be freed. */
+
             /* Take the request off the list of running requests */
             if (l2meta->nb_clusters != 0) {
                 QLIST_REMOVE(l2meta, next_in_flight);
@@ -1103,6 +1111,13 @@ fail:
     while (l2meta != NULL) {
         QCowL2Meta *next;
 
+        /* Undo all leaked allocations */
+        if (l2meta->nb_clusters != 0) {
+            qcow2_free_clusters(bs, l2meta->alloc_offset,
+                                l2meta->nb_clusters << s->cluster_bits,
+                                QCOW2_DISCARD_OTHER);
+        }
+
         if (l2meta->nb_clusters != 0) {
             QLIST_REMOVE(l2meta, next_in_flight);
         }
-- 
1.8.3.1

  reply	other threads:[~2013-10-11  7:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11  7:36 [Qemu-devel] [PATCH v2 0/2] qcow2: Undo leaked allocations in co_writev Max Reitz
2013-10-11  7:36 ` Max Reitz [this message]
2013-10-11  7:36 ` [Qemu-devel] [PATCH v2 2/2] qemu-iotests: Extend test 026 Max Reitz

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=1381476986-3032-2-git-send-email-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --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 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).