From 66d5d91465deba55afa9e1ab3a2160fc9d1b9275 Mon Sep 17 00:00:00 2001 From: Pranith Kumar K Date: Wed, 20 Mar 2013 08:36:14 +0530 Subject: performance/io-threads: Fix range-check for least-rate-limit The issue could be fixed with .validate=GF_OPT_VALIDATE_MIN. But adding max value is more robust. Change-Id: Ia69c6f86855dbd34a26e20391e77bfa0f796a200 BUG: 923573 Signed-off-by: Pranith Kumar K Reviewed-on: http://review.gluster.org/4698 Reviewed-by: Brian Foster Reviewed-by: Jeff Darcy Tested-by: Gluster Build System --- xlators/performance/io-threads/src/io-threads.c | 1 + 1 file changed, 1 insertion(+) (limited to 'xlators/performance/io-threads/src/io-threads.c') diff --git a/xlators/performance/io-threads/src/io-threads.c b/xlators/performance/io-threads/src/io-threads.c index ccbd41194..226c091f1 100644 --- a/xlators/performance/io-threads/src/io-threads.c +++ b/xlators/performance/io-threads/src/io-threads.c @@ -2799,6 +2799,7 @@ struct volume_options options[] = { {.key = {"least-rate-limit"}, .type = GF_OPTION_TYPE_INT, .min = 0, + .max = INT_MAX, .default_value = "0", .description = "Max number of least priority operations to handle " "per-second" -- cgit