diff options
| author | NeilBrown <neilb@suse.de> | 2014-05-28 13:39:23 +1000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-06-11 12:03:24 -0700 |
| commit | d86a5d297deedda0d991e1216ad8817d2d5a3a2b (patch) | |
| tree | dc3c27f8c4c78a97d23b07d39ca857fe874b8cf3 | |
| parent | fe01110735379c9b04f25b356f1a1589ecb9227d (diff) | |
| download | lwn-d86a5d297deedda0d991e1216ad8817d2d5a3a2b.tar.gz lwn-d86a5d297deedda0d991e1216ad8817d2d5a3a2b.zip | |
md: always set MD_RECOVERY_INTR when aborting a reshape or other "resync".
commit 3991b31ea072b070081ca3bfa860a077eda67de5 upstream.
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.
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | drivers/md/md.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/md/md.c b/drivers/md/md.c index 00a99fe797d4..a9cd6d9ec22d 100644 --- a/drivers/md/md.c +++ b/drivers/md/md.c @@ -7338,8 +7338,10 @@ void md_do_sync(struct md_thread *thread) /* just incase thread restarts... */ if (test_bit(MD_RECOVERY_DONE, &mddev->recovery)) return; - if (mddev->ro) /* never try to sync a read-only array */ + if (mddev->ro) {/* never try to sync a read-only array */ + set_bit(MD_RECOVERY_INTR, &mddev->recovery); return; + } if (test_bit(MD_RECOVERY_SYNC, &mddev->recovery)) { if (test_bit(MD_RECOVERY_CHECK, &mddev->recovery)) |