summaryrefslogtreecommitdiffstats
path: root/drivers/misc/atmel-ssc.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-05-26 12:57:21 +1000
committerNeilBrown <neilb@suse.de>2009-05-26 12:57:21 +1000
commit7a91ee1f628ef6bfe3f13067c0ddf9db520cb86b (patch)
treeb6b317a2dfb067784fccae113001cb3957e25337 /drivers/misc/atmel-ssc.c
parent848b3182365fdf5a05bcd5ed949071cac2c894b3 (diff)
downloadblackbird-op-linux-7a91ee1f628ef6bfe3f13067c0ddf9db520cb86b.tar.gz
blackbird-op-linux-7a91ee1f628ef6bfe3f13067c0ddf9db520cb86b.zip
md: don't update curr_resync_completed without also updating reshape_position.
In order for the metadata to always be consistent, we mustn't updated curr_resync_completed without also updating reshape_position. The reshape code updates both at the same time. However since commit 97e4f42d62badb0f9fbc27c013e89bc1336a03bc the common md_do_sync will sometimes update curr_resync_completed but is not in a position to update reshape_position. So if MD_RECOVERY_RESHAPE is set (indicating that a reshape is happening, so reshape_position might change), don't update curr_resync_completed in md_do_sync, leave it to the per-personality reshape code. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/misc/atmel-ssc.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud