commit: 91502f099dfc5a1e8812898e26ee280713e1d002 From: Dan Carpenter <[email protected]> Date: Thu, 11 Oct 2012 14:20:58 +1100 Subject: md/raid10: use correct limit variable
Clang complains that we are assigning a variable to itself. This should be using bad_sectors like the similar earlier check does. Bug has been present since 3.1-rc1. It is minor but could conceivably cause corruption or other bad behaviour. Cc: [email protected] Signed-off-by: Dan Carpenter <[email protected]> Signed-off-by: NeilBrown <[email protected]> --- drivers/md/raid10.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index 146749b..867d1b4 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -3218,7 +3218,7 @@ static sector_t sync_request(struct mddev *mddev, sector_t sector_nr, else { bad_sectors -= (sector - first_bad); if (max_sync > bad_sectors) - max_sync = max_sync; + max_sync = bad_sectors; continue; } } -- 1.7.3.4 -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
