qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, berto@igalia.com, qemu-block@nongnu.org,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH for 3.1 v3 0/3] minor qcow2 compression improvements
Date: Wed, 14 Nov 2018 08:48:15 -0600	[thread overview]
Message-ID: <617cda1f-100b-fa0c-a324-984917967880@redhat.com> (raw)
In-Reply-To: <20181113230319.1008531-1-eblake@redhat.com>

On 11/13/18 5:03 PM, Eric Blake wrote:
> As the added iotests shows, we have a (corner case) data corruption
> that is user triggerable, therefore, this is still appropriate for
> inclusion in 3.1.
> 
> v6 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg08497.html

Wow, I can't count. That was v7, and this email should be titled v8, not 
v3 ;)

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

      parent reply	other threads:[~2018-11-14 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 23:03 [Qemu-devel] [PATCH for 3.1 v3 0/3] minor qcow2 compression improvements Eric Blake
2018-11-13 23:03 ` [Qemu-devel] [PATCH v3 1/3] qcow2: Document some maximum size constraints Eric Blake
2018-11-15 15:17   ` Alberto Garcia
2018-11-15 16:24     ` Eric Blake
2018-11-13 23:03 ` [Qemu-devel] [PATCH v3 2/3] qcow2: Don't allow overflow during cluster allocation Eric Blake
2018-11-13 23:03 ` [Qemu-devel] [PATCH v3 3/3] iotests: Add new test 220 for max compressed cluster offset Eric Blake
2018-11-14 14:35 ` [Qemu-devel] [PATCH for 3.1 v3 0/3] minor qcow2 compression improvements Kevin Wolf
2018-11-15 18:36   ` Eric Blake
2018-11-14 14:48 ` Eric Blake [this message]

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=617cda1f-100b-fa0c-a324-984917967880@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 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).