All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Max Reitz <mreitz@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	vsementsov@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH for-2.11] qcow2: fix image corruption on commit with persistent snapshot
Date: Mon, 20 Nov 2017 15:36:18 +0100	[thread overview]
Message-ID: <20171120143618.GC7197@localhost.localdomain> (raw)
In-Reply-To: <dbb84db4-ead4-e8cf-25c4-fba4dd8701c4@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

Am 17.11.2017 um 19:46 hat Eric Blake geschrieben:
> > -- and I'm not really a fan of testing this on every possible
> > architecture and then adding different reference outputs.
> > 
> > Therefore, the best fix is probably to just filter the hashes out (you
> > don't need the exact value anyway, do you?), and I think it's fine to do
> > this as a follow-up.
> 
> At any rate, I concur with this conclusion; I'll post a followup that
> filters out the hash (for this test, we only care that the existence of
> a hash proves the bitmap exists; unlike 165 where we want to validate
> that it is actually tracking correct information).
> 
> I missed Kevin's -rc2 pull, unless he wants to send a v2; but we also
> have time (it's not the end of the world if the fix goes in -rc3).

There is no rule that a maintainer can only send one pull request per
release candidate. I already missed -rc1, so I wanted to make sure to
get things merged definitely in time for -rc2, but it's not too unlikely
that I'll send another small pull request for tomorrow.

Kevin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      parent reply	other threads:[~2017-11-20 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 16:47 [Qemu-devel] [PATCH for-2.11] qcow2: fix image corruption on commit with persistent snapshot Eric Blake
2017-11-17 17:07 ` Vladimir Sementsov-Ogievskiy
2017-11-17 17:11   ` Eric Blake
2017-11-17 17:24   ` Kevin Wolf
2017-11-17 17:19 ` Kevin Wolf
2017-11-17 18:17 ` Max Reitz
2017-11-17 18:46   ` Eric Blake
2017-11-17 18:55     ` Eric Blake
2017-11-20 14:36     ` Kevin Wolf [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=20171120143618.GC7197@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    /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.