From: Eric Blake <eblake@redhat.com> To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org, mreitz@redhat.com Subject: Re: [Qemu-devel] [PATCH] qcow2: Fix qcow2_make_empty() with external data file Date: Mon, 29 Apr 2019 09:40:40 -0500 [thread overview] Message-ID: <ab303a48-a796-4550-f6cf-cff2674d2ee9@redhat.com> (raw) In-Reply-To: <20190429112140.GF8492@localhost.localdomain> [-- Attachment #1: Type: text/plain, Size: 1075 bytes --] On 4/29/19 6:21 AM, Kevin Wolf wrote: > Am 29.04.2019 um 12:57 hat Kevin Wolf geschrieben: >> make_completely_empty() is an optimisated path for bdrv_make_empty() >> where completely new metadata is created inside the image file instead >> of going through all clusters and discarding them. For an external data >> file, however, we actually need to do discard operations on the data >> file; just overwriting the qcow2 file doesn't get rid of the data. >> >> The necessary slow path with an explicit discard operation already >> exists for other cases. Use it for external data files, too. >> >> Cc: qemu-stable@nongnu.org >> Signed-off-by: Kevin Wolf <kwolf@redhat.com> >> --- >> block/qcow2.c | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) > Oops, I hadn't everything committed yet. I'll add a comment change as > well: With the comment change squashed in, Reviewed-by: Eric Blake <eblake@redhat.com> -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com> To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org Cc: mreitz@redhat.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org Subject: Re: [Qemu-devel] [PATCH] qcow2: Fix qcow2_make_empty() with external data file Date: Mon, 29 Apr 2019 09:40:40 -0500 [thread overview] Message-ID: <ab303a48-a796-4550-f6cf-cff2674d2ee9@redhat.com> (raw) Message-ID: <20190429144040.rPU_vQZQJz6xLEwcjJCvGJfb9fpS3cbFS2FTv8hehBo@z> (raw) In-Reply-To: <20190429112140.GF8492@localhost.localdomain> [-- Attachment #1: Type: text/plain, Size: 1075 bytes --] On 4/29/19 6:21 AM, Kevin Wolf wrote: > Am 29.04.2019 um 12:57 hat Kevin Wolf geschrieben: >> make_completely_empty() is an optimisated path for bdrv_make_empty() >> where completely new metadata is created inside the image file instead >> of going through all clusters and discarding them. For an external data >> file, however, we actually need to do discard operations on the data >> file; just overwriting the qcow2 file doesn't get rid of the data. >> >> The necessary slow path with an explicit discard operation already >> exists for other cases. Use it for external data files, too. >> >> Cc: qemu-stable@nongnu.org >> Signed-off-by: Kevin Wolf <kwolf@redhat.com> >> --- >> block/qcow2.c | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) > Oops, I hadn't everything committed yet. I'll add a comment change as > well: With the comment change squashed in, Reviewed-by: Eric Blake <eblake@redhat.com> -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-29 14:40 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-29 10:57 [Qemu-devel] [PATCH] qcow2: Fix qcow2_make_empty() with external data file Kevin Wolf 2019-04-29 10:57 ` Kevin Wolf 2019-04-29 11:21 ` Kevin Wolf 2019-04-29 11:21 ` Kevin Wolf 2019-04-29 14:40 ` Eric Blake [this message] 2019-04-29 14:40 ` Eric Blake 2019-04-29 16:13 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi 2019-04-29 16:13 ` Stefan Hajnoczi 2019-04-30 13:54 ` [Qemu-devel] " no-reply 2019-04-30 13:54 ` no-reply 2019-04-30 15:32 ` Eric Blake 2019-04-30 15:32 ` Eric Blake 2019-04-30 15:42 ` no-reply 2019-04-30 15:42 ` no-reply
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=ab303a48-a796-4550-f6cf-cff2674d2ee9@redhat.com \ --to=eblake@redhat.com \ --cc=kwolf@redhat.com \ --cc=mreitz@redhat.com \ --cc=qemu-block@nongnu.org \ --cc=qemu-devel@nongnu.org \ --cc=qemu-stable@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: linkBe 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).