From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] qcow2: Fix crash during copy_sectors() after corruption
Date: Tue, 11 Mar 2014 11:21:27 +0100 [thread overview]
Message-ID: <20140311102127.GC3215@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1394491449-10897-1-git-send-email-mreitz@redhat.com>
Am 10.03.2014 um 23:44 hat Max Reitz geschrieben:
> This series fixes a call to a NULL function pointer during
> copy_sectors(), if a concurrent write request triggered the corruption
> prevention mechanism.
>
>
> Max Reitz (3):
> qcow2: Check bs->drv in copy_sectors()
> block: bs->drv may be NULL in bdrv_debug_resume()
> iotests: Test corruption during COW request
>
> block.c | 2 +-
> block/qcow2-cluster.c | 4 ++++
> tests/qemu-iotests/060 | 26 ++++++++++++++++++++++++++
> tests/qemu-iotests/060.out | 15 +++++++++++++++
> 4 files changed, 46 insertions(+), 1 deletion(-)
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
next prev parent reply other threads:[~2014-03-11 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 22:44 [Qemu-devel] [PATCH 0/3] qcow2: Fix crash during copy_sectors() after corruption Max Reitz
2014-03-10 22:44 ` [Qemu-devel] [PATCH 1/3] qcow2: Check bs->drv in copy_sectors() Max Reitz
2014-03-10 23:16 ` Laszlo Ersek
2014-03-11 10:16 ` Kevin Wolf
2014-03-11 14:04 ` Paolo Bonzini
2014-03-11 18:19 ` Max Reitz
2014-03-11 18:09 ` Max Reitz
2014-03-10 22:44 ` [Qemu-devel] [PATCH 2/3] block: bs->drv may be NULL in bdrv_debug_resume() Max Reitz
2014-03-10 22:44 ` [Qemu-devel] [PATCH 3/3] iotests: Test corruption during COW request Max Reitz
2014-03-11 10:21 ` Kevin Wolf [this message]
2014-03-11 13:13 ` [Qemu-devel] [PATCH 0/3] qcow2: Fix crash during copy_sectors() after corruption Stefan Hajnoczi
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=20140311102127.GC3215@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).