From: Stefan Hajnoczi <stefanha@gmail.com>
To: Asias He <asias@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [PATCH v2] block: Produce zeros when protocols reading beyond end of file
Date: Thu, 22 Aug 2013 14:13:28 +0200 [thread overview]
Message-ID: <20130822121328.GG27613@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1375754020-20545-1-git-send-email-asias@redhat.com>
On Tue, Aug 06, 2013 at 09:53:40AM +0800, Asias He wrote:
> From: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
>
> While Asias is debugging an issue creating qcow2 images on top of
> non-file protocols. It boils down to this example using NBD:
>
> $ qemu-io -c 'open -g nbd+unix:///?socket=/tmp/nbd.sock' -c 'read -v 0 512'
>
> Notice the open -g option to set bs->growable. This means you can
> read/write beyond end of file. Reading beyond end of file is supposed
> to produce zeroes.
>
> We rely on this behavior in qcow2_create2() during qcow2 image
> creation. We create a new file and then write the qcow2 header
> structure using bdrv_pwrite(). Since QCowHeader is not a multiple of
> sector size, block.c first uses bdrv_read() on the empty file to fetch
> the first sector (should be all zeroes).
>
> Here is the output from the qemu-io NBD example above:
>
> $ qemu-io -c 'open -g nbd+unix:///?socket=/tmp/nbd.sock' -c 'read -v 0 512'
> 00000000: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ................
> 00000010: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ................
> 00000020: ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ab ................
> ...
>
> We are not zeroing the buffer! As a result qcow2 image creation on top
> of protocols is not guaranteed to work even when file creation is
> supported by the protocol.
>
> Signed-off-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> Signed-off-by: Asias He <asias@redhat.com>
> ---
> block.c | 30 +++++++++++++++++++++++++++++-
> 1 file changed, 29 insertions(+), 1 deletion(-)
Applied again on top of Asias' fix so qcow2 vmstate doesn't break.
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
next prev parent reply other threads:[~2013-08-22 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 8:11 [Qemu-devel] [PATCH] block: Produce zeros when protocols reading beyond end of file Asias He
2013-08-05 12:41 ` Kevin Wolf
2013-08-06 1:53 ` [Qemu-devel] [PATCH v2] " Asias He
2013-08-06 2:02 ` Fam Zheng
2013-08-06 2:38 ` Asias He
2013-08-07 8:04 ` Stefan Hajnoczi
2013-08-13 13:50 ` Stefan Hajnoczi
2013-08-22 12:13 ` Stefan Hajnoczi [this message]
2013-08-16 8:41 ` [Qemu-devel] [PATCH] " Stefan Hajnoczi
2013-08-19 6:36 ` Asias He
2013-08-19 12:09 ` 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=20130822121328.GG27613@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=asias@redhat.com \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--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).