diff options
| author | Yu Kuai <yukuai3@huawei.com> | 2023-05-12 03:56:06 +0200 |
|---|---|---|
| committer | Song Liu <song@kernel.org> | 2023-06-14 00:13:20 +0200 |
| commit | 46038b30b308c3ebf49e79548f109d00a8d74b31 (patch) | |
| tree | d19ec2b9000bfd0be0735c9c743ba72c4791fa1f /drivers/md | |
| parent | md/raid10: check slab-out-of-bounds in md_bitmap_get_counter (diff) | |
| download | linux-46038b30b308c3ebf49e79548f109d00a8d74b31.tar.xz linux-46038b30b308c3ebf49e79548f109d00a8d74b31.zip | |
md/raid5: don't allow replacement while reshape is in progress
If reshape is interrupted(for example, echo frozen to sync_action), then
rdev replacement can be set. It's safe because reshape is always prior to
resync in md_check_recovery(). However, if system reboots, then kernel will
complain cannot handle concurrent replacement and reshape and this array
is not able to assemble anymore.
Fix this problem by don't allow replacement until reshape is done.
Reported-by: Peter Neuwirth <reddunur@online.de>
Link: https://lore.kernel.org/linux-raid/e2f96772-bfbc-f43b-6da1-f520e5164536@online.de/
Signed-off-by: Yu Kuai <yukuai3@huawei.com>
Signed-off-by: Song Liu <song@kernel.org>
Link: https://lore.kernel.org/r/20230512015610.821290-2-yukuai1@huaweicloud.com
Diffstat (limited to 'drivers/md')
| -rw-r--r-- | drivers/md/raid5.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 4739ed891e75..5950932323fc 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -8377,6 +8377,7 @@ static int raid5_add_disk(struct mddev *mddev, struct md_rdev *rdev) p = conf->disks + disk; tmp = rdev_mdlock_deref(mddev, p->rdev); if (test_bit(WantReplacement, &tmp->flags) && + mddev->reshape_position == MaxSector && p->replacement == NULL) { clear_bit(In_sync, &rdev->flags); set_bit(Replacement, &rdev->flags); |