From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] block: Warn about usage of growing formats over non-growable protocols
Date: Sat, 12 Jul 2014 00:23:03 +0200 [thread overview]
Message-ID: <1405117387-25539-1-git-send-email-mreitz@redhat.com> (raw)
Some image formats (e.g. qcow2) require the underlying file to grow on
write accesses, but this is in fact not supported by all protocols (e.g.
nbd does not). If such a format requiring file growth is used
non-read-only over a protocol which does not support this, a warning
should be issued.
This warning is issued for example whenever one tries to export a qcow2
image over nbd-server and use the export from qemu.
We could make this an error, but I decided not to in order to retain
"compatibility" (although if this warning is emitted, the user should
have already complained about I/O errors on write accesses, so it's
questionable what behavior this should be compatible to).
While at it, make BDS.growable actually indicate what it is (as far as I
understood) supposed to: Whether the BDS supports writes beyond the end
of the disk size (which then automatically increase that disk size).
Max Reitz (4):
block: Correct bs->growable
block: Introduce requires_growing_file
iotests: Make some qemu-io commands read-only
iotests: Skip read and write in 040 for length=0
block.c | 11 +++++++++++
block/blkdebug.c | 2 ++
block/blkverify.c | 2 ++
block/cow.c | 1 +
block/iscsi.c | 2 ++
block/nbd.c | 2 ++
block/qcow.c | 1 +
block/qcow2.c | 2 ++
block/qed.c | 1 +
block/raw_bsd.c | 1 +
block/vdi.c | 2 ++
block/vhdx.c | 2 ++
block/vmdk.c | 1 +
block/vpc.c | 2 ++
include/block/block_int.h | 4 ++++
tests/qemu-iotests/040 | 18 +++++++++++-------
tests/qemu-iotests/072 | 9 ++++++++-
tests/qemu-iotests/072.out | 1 +
tests/qemu-iotests/089 | 2 +-
19 files changed, 57 insertions(+), 9 deletions(-)
--
2.0.1
next reply other threads:[~2014-07-11 22:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 22:23 Max Reitz [this message]
2014-07-11 22:23 ` [Qemu-devel] [PATCH 1/4] block: Correct bs->growable Max Reitz
2014-08-20 11:40 ` Kevin Wolf
2014-08-20 19:13 ` Max Reitz
2014-08-21 8:19 ` Kevin Wolf
2014-08-22 13:26 ` Max Reitz
2014-09-04 20:01 ` Max Reitz
2014-09-05 10:01 ` Kevin Wolf
2014-09-05 12:46 ` Max Reitz
2014-09-05 13:13 ` Kevin Wolf
2014-07-11 22:23 ` [Qemu-devel] [PATCH 2/4] block: Introduce requires_growing_file Max Reitz
2014-07-11 22:23 ` [Qemu-devel] [PATCH 3/4] iotests: Make some qemu-io commands read-only Max Reitz
2014-07-11 22:23 ` [Qemu-devel] [PATCH 4/4] iotests: Skip read and write in 040 for length=0 Max Reitz
2014-08-15 15:23 ` [Qemu-devel] [PATCH 0/4] block: Warn about usage of growing formats over non-growable protocols Max Reitz
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=1405117387-25539-1-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).