From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: berto@igalia.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] qcow2: Fix cluster leaks on write error
Date: Thu, 28 Jun 2018 18:11:14 +0200 [thread overview]
Message-ID: <b247d3da-72f0-f1ae-3642-c42c2150ce8d@redhat.com> (raw)
In-Reply-To: <20180628153937.26097-1-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On 2018-06-28 17:39, Kevin Wolf wrote:
> Kevin Wolf (3):
> qemu-iotests: Update 026.out.nocache reference output
> qcow2: Free allocated clusters on write error
> qemu-iotests: Test qcow2 not leaking clusters on write error
>
> block/qcow2.h | 1 +
> block/qcow2-cluster.c | 11 +++++++++++
> block/qcow2.c | 2 ++
> tests/qemu-iotests/026 | 17 +++++++++++++++++
> tests/qemu-iotests/026.out | 8 ++++++++
> tests/qemu-iotests/026.out.nocache | 14 +++++++++++---
> 6 files changed, 50 insertions(+), 3 deletions(-)
Reviewed-by: Max Reitz <mreitz@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-06-28 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 15:39 [Qemu-devel] [PATCH 0/3] qcow2: Fix cluster leaks on write error Kevin Wolf
2018-06-28 15:39 ` [Qemu-devel] [PATCH 1/3] qemu-iotests: Update 026.out.nocache reference output Kevin Wolf
2018-06-28 15:39 ` [Qemu-devel] [PATCH 2/3] qcow2: Free allocated clusters on write error Kevin Wolf
2018-06-28 15:49 ` Eric Blake
2018-06-28 18:53 ` Eric Blake
2018-06-28 15:39 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: Test qcow2 not leaking " Kevin Wolf
2018-06-28 16:11 ` Max Reitz [this message]
2018-06-29 7:26 ` [Qemu-devel] [PATCH 0/3] qcow2: Fix cluster leaks " Kevin Wolf
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=b247d3da-72f0-f1ae-3642-c42c2150ce8d@redhat.com \
--to=mreitz@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@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).