Markus Armbruster f70edf9948 blockdev: Clean up fragile use of error_is_set()
Using error_is_set(ERRP) to find out whether a function failed is
either wrong, fragile, or unnecessarily opaque.  It's wrong when ERRP
may be null, because errors go undetected when it is.  It's fragile
when proving ERRP non-null involves a non-local argument.  Else, it's
unnecessarily opaque (see commit 84d18f0).

The error_is_set(errp) in internal_snapshot_prepare() is merely
fragile, because the caller never passes a null errp argument.

Make the code more robust and more obviously correct: receive the
error in a local variable, then propagate it through the parameter.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2014-04-25 18:05:06 +02:00
2014-04-23 10:28:14 +02:00
2014-04-25 12:22:37 +01:00
2014-04-25 12:22:37 +01:00
2014-03-25 14:09:50 +01:00
2014-04-24 15:24:52 +01:00
2014-03-28 13:46:29 +00:00
2014-03-27 15:19:00 +05:30
2014-04-18 10:33:36 +04:00
2014-03-27 15:19:00 +05:30
2014-04-22 12:00:20 +02:00
2014-04-22 12:00:20 +02:00
2014-03-27 15:19:00 +05:30
2014-04-23 10:28:14 +02:00
2014-04-17 20:39:32 +01:00
2014-03-27 15:19:00 +05:30

Read the documentation in qemu-doc.html or on http://wiki.qemu-project.org

- QEMU team
Description
No description provided
Readme 404 MiB
Languages
C 82.6%
C++ 6.5%
Python 3.4%
Dylan 2.9%
Shell 1.6%
Other 2.8%