From: Kevin Wolf <kwolf@redhat.com>
To: Michael Weiser <michael@weiser.dinsnail.net>
Cc: psyhomb@gmail.com, vsementsov@virtuozzo.com, den@virtuozzo.com,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
qemu-stable@nongnu.org, dgilbert@redhat.com, mreitz@redhat.com,
lersek@redhat.com
Subject: Re: [PATCH 2/3] qcow2: Assert that qcow2_cache_get() callers hold s->lock
Date: Fri, 25 Oct 2019 14:42:09 +0200 [thread overview]
Message-ID: <20191025124209.GD7275@localhost.localdomain> (raw)
In-Reply-To: <20191025103510.GA2272@weiser.dinsnail.net>
Am 25.10.2019 um 12:35 hat Michael Weiser geschrieben:
> I was going to test with master as well but got overtaken by v2. Will
> move on to test v2 now. :)
>
> Series:
> Tested-by: Michael Weiser <michael.weiser@gmx.de>
Thanks for testing!
The fix itself is unchanged in v2, so I assume the result will be the
same, but testing it explicitly can't hurt. I'm going to send a pull
request today, but if you're quick, I can wait for your results.
> No biggie but if there's a chance could you switch my address to the
> above?
No problem, I've updated the address in the Reported-by tag.
Kevin
next prev parent reply other threads:[~2019-10-25 12:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 15:26 [PATCH 0/3] qcow2: Fix image corruption bug in 4.1 Kevin Wolf
2019-10-23 15:26 ` [PATCH 1/3] coroutine: Add qemu_co_mutex_assert_locked() Kevin Wolf
2019-10-24 9:59 ` Denis Lunev
2019-10-24 10:54 ` Kevin Wolf
2019-10-24 11:11 ` Denis Lunev
2019-10-23 15:26 ` [PATCH 2/3] qcow2: Assert that qcow2_cache_get() callers hold s->lock Kevin Wolf
2019-10-23 15:37 ` Kevin Wolf
2019-10-25 10:35 ` Michael Weiser
2019-10-25 12:42 ` Kevin Wolf [this message]
2019-10-24 10:01 ` Denis Lunev
2019-10-24 10:57 ` Kevin Wolf
2019-10-24 11:14 ` Denis Lunev
2019-10-24 12:07 ` Kevin Wolf
2019-10-24 13:03 ` Vladimir Sementsov-Ogievskiy
2019-10-24 13:17 ` Kevin Wolf
2019-10-23 15:26 ` [PATCH 3/3] qcow2: Fix corruption bug in qcow2_detect_metadata_preallocation() Kevin Wolf
2019-10-24 10:46 ` Vladimir Sementsov-Ogievskiy
2019-10-24 11:17 ` Kevin Wolf
2019-10-24 12:41 ` Vladimir Sementsov-Ogievskiy
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=20191025124209.GD7275@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=den@virtuozzo.com \
--cc=dgilbert@redhat.com \
--cc=lersek@redhat.com \
--cc=michael@weiser.dinsnail.net \
--cc=mreitz@redhat.com \
--cc=psyhomb@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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).