diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2013-06-26 09:41:57 +0200 |
|---|---|---|
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2013-08-12 15:26:48 -0500 |
| commit | eedc9f46cfae88428e31e809e396eacc5d800a4f (patch) | |
| tree | 4ea06a601784794339977215c8d146c067eced5a /arch_init.c | |
| parent | 90ce84993a1590074ce9b866ca389bb40b4f13b7 (diff) | |
gluster: Return bdrv_has_zero_init = 0
GlusterFS volumes can be backed by block devices, in which case
bdrv_create() doesn't make sure that the image is zeroed out. It is
currently not possibly to detect whether a given image is backed by a
file or a block device, and incorrectly assuming that it is zeroed
corrupts images during qemu-img convert, so let's err on the side of
caution and always return 0.
Cc: qemu-stable@nongnu.org
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
(cherry picked from commit 8ab6feec2c7500faafd9a4571fb40d03dd360a64)
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'arch_init.c')
0 files changed, 0 insertions, 0 deletions