summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid10.c
diff options
context:
space:
mode:
authorDan Carpenter <dan.carpenter@oracle.com>2012-10-11 05:20:58 +0200
committerNeilBrown <neilb@suse.de>2012-10-11 05:20:58 +0200
commit91502f099dfc5a1e8812898e26ee280713e1d002 (patch)
tree7e38d225da477345f674739ecf3aefec3c44307c /drivers/md/raid10.c
parentmd: writing to sync_action should clear the read-auto state. (diff)
downloadlinux-91502f099dfc5a1e8812898e26ee280713e1d002.tar.xz
linux-91502f099dfc5a1e8812898e26ee280713e1d002.zip
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: stable@vger.kernel.org Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to '')
-rw-r--r--drivers/md/raid10.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index 146749b277c6..867d1b4e9634 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;
}
}