NeilBrown 2ac295a544 md: always set MD_RECOVERY_INTR when interrupting a reshape thread.
Commit 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97
   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: 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97
Cc: stable@vger.kernel.org (3.2+)
Signed-off-by: NeilBrown <neilb@suse.de>
2014-05-29 16:59:06 +10:00
..
2013-03-01 22:45:51 +00:00
2013-03-01 22:45:51 +00:00
2014-01-14 23:23:03 -05:00
2013-11-23 22:33:47 -08:00
2013-11-09 18:20:22 -05:00
2013-08-23 09:02:13 -04:00
2013-11-23 22:33:47 -08:00
2012-07-30 17:25:16 -07:00
2013-09-05 20:46:06 -04:00
2013-11-23 22:33:47 -08:00
2013-11-23 22:33:47 -08:00
2014-01-14 23:23:04 -05:00
2013-03-01 22:45:47 +00:00
2014-03-27 16:56:24 -04:00
2014-03-27 16:56:24 -04:00
2013-11-23 22:33:47 -08:00
2014-03-27 16:56:23 -04:00
2013-11-23 22:33:57 -08:00
2014-03-27 16:56:23 -04:00
2013-11-23 22:33:47 -08:00
2013-11-23 22:33:57 -08:00
2013-11-20 13:05:25 -08:00