diff options
| author | Eric Blake | 2017-03-08 22:34:28 +0100 |
|---|---|---|
| committer | Kevin Wolf | 2017-03-13 12:49:33 +0100 |
| commit | 6f712ee08036f4e8066cdddcfed288bf01914e55 (patch) | |
| tree | 3bfcd926750194275ca58e8bf0e69ada915627c7 /migration | |
| parent | backup: React to bdrv_is_allocated() errors (diff) | |
| download | qemu-6f712ee08036f4e8066cdddcfed288bf01914e55.tar.gz qemu-6f712ee08036f4e8066cdddcfed288bf01914e55.tar.xz qemu-6f712ee08036f4e8066cdddcfed288bf01914e55.zip | |
vvfat: React to bdrv_is_allocated() errors
If bdrv_is_allocated() fails, we should react to that failure.
For 2 of the 3 callers, reporting the error was easy. But in
cluster_was_modified() and its lone caller
get_cluster_count_for_direntry(), it's rather invasive to update
the logic to pass the error back; so there, I went with merely
documenting the issue by changing the return type to bool (in
all likelihood, treating the cluster as modified will then
trigger a read which will also fail, and eventually get to an
error - but given the appalling number of abort() calls in this
code, I'm not making it any worse).
Signed-off-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'migration')
0 files changed, 0 insertions, 0 deletions