[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 4/5] blockdev: Clean up fragile use of error_is_
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-devel] [PATCH 4/5] blockdev: Clean up fragile use of error_is_set() |
Date: |
Thu, 24 Apr 2014 12:20:54 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Am 24.04.2014 um 11:15 hat Markus Armbruster geschrieben:
> 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 <address@hidden>
Reviewed-by: Kevin Wolf <address@hidden>
- [Qemu-devel] [PATCH 1/5] Use error_is_set() only when necessary (again), (continued)
- [Qemu-devel] [PATCH 1/5] Use error_is_set() only when necessary (again), Markus Armbruster, 2014/04/24
- [Qemu-devel] [PATCH 3/5] nbd: Use return values instead of error_is_set(errp), Markus Armbruster, 2014/04/24
- [Qemu-devel] [PATCH 2/5] qemu-img: Consistently name Error * objects err, and not errp, Markus Armbruster, 2014/04/24
- [Qemu-devel] [PATCH 5/5] iscsi: Don't use error_is_set() to suppress additional errors, Markus Armbruster, 2014/04/24
- [Qemu-devel] [PATCH 4/5] blockdev: Clean up fragile use of error_is_set(), Markus Armbruster, 2014/04/24
- Re: [Qemu-devel] [PATCH 4/5] blockdev: Clean up fragile use of error_is_set(),
Kevin Wolf <=