From: Kevin Wolf <kwolf@redhat.com>
Date: Wed, 16 Jan 2013 20:20:00 +0000 (+0100)
Subject: win32-aio: Fix memory leak
X-Git-Tag: qemu-xen-4.3.0~6^2~6
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=563068a8b2e980713e056512bcd941237f6090fb;p=qemu-upstream-4.3-testing.git

win32-aio: Fix memory leak

The buffer is allocated for both reads and writes, and obviously it
should be freed even if an error occurs.

Cc: qemu-stable@nongnu.org
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
(cherry picked from commit e8bccad5ac6095b5af7946cd72d9aacb57f7c0a3)

Conflicts:

	block/win32-aio.c

*addressed conflict due to buggy g_free() still in use instead of
qemu_vfree() as it is upstream (via commit 7479acdb)

Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
---

diff --git a/block/win32-aio.c b/block/win32-aio.c
index 6b0270725..9b79633e6 100644
--- a/block/win32-aio.c
+++ b/block/win32-aio.c
@@ -87,8 +87,8 @@ static void win32_aio_process_completion(QEMUWin32AIOState *s,
                 memcpy(qiov->iov[i].iov_base, p, qiov->iov[i].iov_len);
                 p += qiov->iov[i].iov_len;
             }
-            g_free(waiocb->buf);
         }
+        qemu_vfree(waiocb->buf);
     }