From: NeilBrown Date: Wed, 28 May 2014 03:39:23 +0000 (+1000) Subject: md: always set MD_RECOVERY_INTR when aborting a reshape or other "resync". X-Git-Tag: omap-for-v3.16/fixes-against-rc1~108^2~1 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3991b31ea072b070081ca3bfa860a077eda67de5;p=pandora-kernel.git md: always set MD_RECOVERY_INTR when aborting a reshape or other "resync". If mddev->ro is set, md_to_sync will (correctly) abort. However in that case MD_RECOVERY_INTR isn't set. If a RESHAPE had been requested, then ->finish_reshape() will be called and it will think the reshape was successful even though nothing happened. Normally a resync will not be requested if ->ro is set, but if an array is stopped while a reshape is on-going, then when the array is started, the reshape will be restarted. If the array is also set read-only at this point, the reshape will instantly appear to success, resulting in data corruption. Consequently, this patch is suitable for any -stable kernel. Cc: stable@vger.kernel.org (any) Signed-off-by: NeilBrown --- Reading git-diff-tree failed