diff options
| author | Hanna Reitz <hreitz@redhat.com> | 2021-10-26 11:07:45 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2021-11-02 13:22:09 +0100 |
| commit | 73d4a11300ee87e04f93fab4380b80379e792a06 (patch) | |
| tree | 3fa3e5fbeeaa0f1d91c9e68e2376ad4d61aa4a60 /block | |
| parent | 68d7946648a5c364a4df187804d37f09a318b50f (diff) | |
| download | qemu-73d4a11300ee87e04f93fab4380b80379e792a06.zip qemu-73d4a11300ee87e04f93fab4380b80379e792a06.tar.gz qemu-73d4a11300ee87e04f93fab4380b80379e792a06.tar.bz2 | |
block-backend: Silence clang -m32 compiler warning
Similarly to e7e588d432d31ecebc26358e47201dd108db964c, there is a
warning in block/block-backend.c that qiov->size <= INT64_MAX is always
true on machines where size_t is narrower than a uint64_t. In said
commit, we silenced this warning by casting to uint64_t.
The commit introducing this warning here
(a93d81c84afa717b0a1a6947524d8d1fbfd6bbf5) anticipated it and so tried
to address it the same way. However, it only did so in one of two
places where this comparison occurs, and so we still need to fix up the
other one.
Fixes: a93d81c84afa717b0a1a6947524d8d1fbfd6bbf5
("block-backend: convert blk_aio_ functions to int64_t bytes
paramter")
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20211026090745.30800-1-hreitz@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block')
| -rw-r--r-- | block/block-backend.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/block-backend.c b/block/block-backend.c index 39cd99d..12ef80e 100644 --- a/block/block-backend.c +++ b/block/block-backend.c @@ -1540,7 +1540,7 @@ BlockAIOCB *blk_aio_pwritev(BlockBackend *blk, int64_t offset, QEMUIOVector *qiov, BdrvRequestFlags flags, BlockCompletionFunc *cb, void *opaque) { - assert(qiov->size <= INT64_MAX); + assert((uint64_t)qiov->size <= INT64_MAX); return blk_aio_prwv(blk, offset, qiov->size, qiov, blk_aio_write_entry, flags, cb, opaque); } |