Files
linux/drivers/md
NeilBrown 88580b125a md: always set MD_RECOVERY_INTR when interrupting a reshape thread.
commit 2ac295a544 upstream.

Commit 8313b8e57f
   md: fix problem when adding device to read-only array with bitmap.

added a called to md_reap_sync_thread() which cause a reshape thread
to be interrupted (in particular, it could cause md_thread() to never even
call md_do_sync()).
However it didn't set MD_RECOVERY_INTR so ->finish_reshape() would not
know that the reshape didn't complete.

This only happens when mddev->ro is set and normally reshape threads
don't run in that situation.  But raid5 and raid10 can start a reshape
thread during "run" is the array is in the middle of a reshape.
They do this even if ->ro is set.

So it is best to set MD_RECOVERY_INTR before abortingg the
sync thread, just in case.

Though it rare for this to trigger a problem it can cause data corruption
because the reshape isn't finished properly.
So it is suitable for any stable which the offending commit was applied to.
(3.2 or later)

Fixes: 8313b8e57f
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-06-11 12:03:24 -07:00
..
2014-02-06 11:08:16 -08:00
2013-04-24 11:42:41 +10:00
2013-03-01 22:45:51 +00:00
2013-03-01 22:45:51 +00:00
2012-03-28 18:41:29 +01:00
2013-03-01 22:45:51 +00:00
2012-07-30 17:25:16 -07:00
2014-02-13 13:48:02 -08:00
2013-03-01 22:45:47 +00:00
2014-02-13 13:48:02 -08:00
2014-02-13 13:48:02 -08:00
2013-03-23 14:15:29 -07:00
2014-02-13 13:48:02 -08:00
2013-03-23 14:15:29 -07:00
2014-02-13 13:48:02 -08:00