summaryrefslogtreecommitdiff
path: root/security/keys
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.com>2015-10-31 11:00:56 +1100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-11-09 12:50:26 -0800
commit74d1fb7a3f4a9208ab9eb7b7cec54ca6cfcb33eb (patch)
tree96d894e3571158d684ea0d1401c815018a61c212 /security/keys
parent29f33397b3fd79a46771afd210fabadc0b71a7ea (diff)
Revert "md: allow a partially recovered device to be hot-added to an array."
commit d01552a76d71f9879af448e9142389ee9be6e95b upstream. This reverts commit 7eb418851f3278de67126ea0c427641ab4792c57. This commit is poorly justified, I can find not discusison in email, and it clearly causes a problem. If a device which is being recovered fails and is subsequently re-added to an array, there could easily have been changes to the array *before* the point where the recovery was up to. So the recovery must start again from the beginning. If a spare is being recovered and fails, then when it is re-added we really should do a bitmap-based recovery up to the recovery-offset, and then a full recovery from there. Before this reversion, we only did the "full recovery from there" which is not corect. After this reversion with will do a full recovery from the start, which is safer but not ideal. It will be left to a future patch to arrange the two different styles of recovery. Reported-and-tested-by: Nate Dailey <nate.dailey@stratus.com> Signed-off-by: NeilBrown <neilb@suse.com> Fixes: 7eb418851f32 ("md: allow a partially recovered device to be hot-added to an array.") Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security/keys')
0 files changed, 0 insertions, 0 deletions