md/raid5: set reshape_position correctly when reshape starts.

As the internal reshape_progress counter is the main driver
for reshape, the fact that reshape_position sometimes starts with the
wrong value has minimal effect. It is visible in sysfs and that
is all.

Signed-off-by: NeilBrown <neilb@suse.de>

NeilBrown e516402c 70471daf

+1 -1
+1 -1
drivers/md/raid5.c
··· 5000 spin_unlock_irqrestore(&conf->device_lock, flags); 5001 } 5002 mddev->raid_disks = conf->raid_disks; 5003 - mddev->reshape_position = 0; 5004 set_bit(MD_CHANGE_DEVS, &mddev->flags); 5005 5006 clear_bit(MD_RECOVERY_SYNC, &mddev->recovery);
··· 5000 spin_unlock_irqrestore(&conf->device_lock, flags); 5001 } 5002 mddev->raid_disks = conf->raid_disks; 5003 + mddev->reshape_position = conf->reshape_progress; 5004 set_bit(MD_CHANGE_DEVS, &mddev->flags); 5005 5006 clear_bit(MD_RECOVERY_SYNC, &mddev->recovery);