All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: berto@igalia.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] qcow2: Free allocated clusters on write error
Date: Thu, 28 Jun 2018 13:53:38 -0500	[thread overview]
Message-ID: <577ae4db-3e41-2c58-dd94-2e5790e047ea@redhat.com> (raw)
In-Reply-To: <b0aa3ea2-c91e-3534-248e-b64791fb39ae@redhat.com>

On 06/28/2018 10:49 AM, Eric Blake wrote:
> On 06/28/2018 10:39 AM, Kevin Wolf wrote:
>> If we managed to allocate the clusters, but then failed to write the
>> data, there's a good chance that we'll still be able to free the
>> clusters again in order to avoid cluster leaks (the refcounts are
>> cached, so even if we can't write them out right now, we may be able to
>> do so when the VM is resumed after a werror=stop/enospc pause).
>>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>>   block/qcow2.h         |  1 +
>>   block/qcow2-cluster.c | 11 +++++++++++
>>   block/qcow2.c         |  2 ++
>>   3 files changed, 14 insertions(+)
> 
> Hmm, I wonder if this interacts poorly with my proposed test addition 
> for HUGE images, which is still pending review:
> https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg05488.html
> https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg04542.html
> 
> (time for me to go testing...)

Phew, my test didn't change (but I will go ahead and repost a v7 to fix 
the minor conflict in iotest numbering).

And that means I can also add for this series:

Tested-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-06-28 18:53 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 [this message]
2018-06-28 15:39 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: Test qcow2 not leaking " Kevin Wolf
2018-06-28 16:11 ` [Qemu-devel] [PATCH 0/3] qcow2: Fix cluster leaks " Max Reitz
2018-06-29  7:26 ` 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=577ae4db-3e41-2c58-dd94-2e5790e047ea@redhat.com \
    --to=eblake@redhat.com \
    --cc=berto@igalia.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 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.