From: Alberto Garcia <be...@igalia.com> Setting FOO_max to a value that is lower than FOO does not make sense, and it produces odd results depending on the value of FOO_max_length. Although the user should not set that configuration in the first place it's better to reject it explicitly.
https://bugzilla.redhat.com/show_bug.cgi?id=1355665 Signed-off-by: Alberto Garcia <be...@igalia.com> Reported-by: Gu Nini <n...@redhat.com> Reviewed-by: Eric Blake <ebl...@redhat.com> Message-id: 663d5aca406060e31f80d8113f77b6feee63b919.1469693110.git.be...@igalia.com Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> --- util/throttle.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/util/throttle.c b/util/throttle.c index 654f95c..3817d9b 100644 --- a/util/throttle.c +++ b/util/throttle.c @@ -348,6 +348,11 @@ bool throttle_is_valid(ThrottleConfig *cfg, Error **errp) " bps/iops values"); return false; } + + if (cfg->buckets[i].max && cfg->buckets[i].max < cfg->buckets[i].avg) { + error_setg(errp, "bps_max/iops_max cannot be lower than bps/iops"); + return false; + } } return true; -- 2.7.4
