diff options
author | Eric Blake <eblake@redhat.com> | 2016-09-07 16:27:20 -0500 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2016-09-22 20:20:51 +0200 |
commit | 95eaa78537c734fa3cb3373d47ba8c0099a36ff0 (patch) | |
tree | a020b649338485f4d8fe0bae001d472c3e74ce14 /block/blkverify.c | |
parent | f8d9ccf8d5f9f4b7d364100871c4c7303b546de5 (diff) | |
download | qemu-95eaa78537c734fa3cb3373d47ba8c0099a36ff0.zip |
iscsi: Fix divide-by-zero regression on raw SG devices
When qemu uses iscsi devices in sg mode, iscsilun->block_size
is left at 0. Prior to commits cf081fca and similar, when
block limits were tracked in sectors, this did not matter:
various block limits were just left at 0. But when we started
scaling by block size, this caused SIGFPE.
Then, in a later patch, commit a5b8dd2c added an assertion to
bdrv_open_common() that request_alignment is always non-zero;
which was not true for SG mode. Rather than relax that assertion,
we can just provide a sane value (we don't know of any SG device
with a block size smaller than qemu's default sizing of 512 bytes).
One possible solution for SG mode is to just blindly skip ALL
of iscsi_refresh_limits(), since we already short circuit so
many other things in sg mode. But this patch takes a slightly
more conservative approach, and merely guarantees that scaling
will succeed, while still using multiples of the original size
where possible. Resulting limits may still be zero in SG mode
(that is, we mostly only fix block_size used as a denominator
or which affect assertions, not all uses).
Reported-by: Holger Schranz <holger@fam-schranz.de>
Signed-off-by: Eric Blake <eblake@redhat.com>
CC: qemu-stable@nongnu.org
Message-Id: <1473283640-15756-1-git-send-email-eblake@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'block/blkverify.c')
0 files changed, 0 insertions, 0 deletions