From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] qcow2: Do not overflow when writing an L1 sector
Date: Wed, 22 Oct 2014 17:31:41 +0200 [thread overview]
Message-ID: <20141022153141.GA5799@noname.str.redhat.com> (raw)
In-Reply-To: <1413465957-20865-1-git-send-email-mreitz@redhat.com>
Am 16.10.2014 um 15:25 hat Max Reitz geschrieben:
> qcow2_write_l1_entry() may read L1 entries from beyond the end of the
> in-memory L1 table when updating a sector. Fix this and add a
> qemu-iotest.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2014-10-22 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 13:25 [Qemu-devel] [PATCH 0/2] qcow2: Do not overflow when writing an L1 sector Max Reitz
2014-10-16 13:25 ` [Qemu-devel] [PATCH 1/2] " Max Reitz
2014-10-20 6:23 ` Peter Lieven
2014-10-16 13:25 ` [Qemu-devel] [PATCH 2/2] iotests: Add test for qcow2 L1 table update Max Reitz
2014-10-20 6:25 ` Peter Lieven
2014-10-20 9:09 ` Max Reitz
2014-10-20 9:18 ` Peter Lieven
2014-10-16 14:54 ` [Qemu-devel] [PATCH 0/2] qcow2: Do not overflow when writing an L1 sector Eric Blake
2014-10-22 15:31 ` 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=20141022153141.GA5799@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pl@kamp.de \
--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).