block: expect get_block_status errors in bdrv_make_zero
authorPeter Lieven <pl@kamp.de>
Thu, 12 Dec 2013 12:57:05 +0000 (13:57 +0100)
committerKevin Wolf <kwolf@redhat.com>
Fri, 13 Dec 2013 13:49:50 +0000 (14:49 +0100)
during testing around with 4k LUNs a bad target implementation
triggert an -EIO in iscsi_get_block_status, but it got never caught
resulting in an infinite loop.

CC: qemu-stable@nongnu.org
Signed-off-by: Peter Lieven <pl@kamp.de>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
block.c

diff --git a/block.c b/block.c
index 13f001ad69a41565e6d10fff75acf7d4b2628520..64e7d220c60a67ca50ddaea952a7ea01c582e2cd 100644 (file)
--- a/block.c
+++ b/block.c
@@ -2421,6 +2421,11 @@ int bdrv_make_zero(BlockDriverState *bs, BdrvRequestFlags flags)
             nb_sectors = INT_MAX;
         }
         ret = bdrv_get_block_status(bs, sector_num, nb_sectors, &n);
+        if (ret < 0) {
+            error_report("error getting block status at sector %" PRId64 ": %s",
+                         sector_num, strerror(-ret));
+            return ret;
+        }
         if (ret & BDRV_BLOCK_ZERO) {
             sector_num += n;
             continue;