md: don't set In_sync if array is frozen
authorGuoqing Jiang <jgq516@gmail.com>
Wed, 24 Jul 2019 09:09:20 +0000 (11:09 +0200)
committerSong Liu <songliubraving@fb.com>
Wed, 7 Aug 2019 17:25:02 +0000 (10:25 -0700)
commit062f5b2ae12a153644c765e7ba3b0f825427be1d
tree14e7072109222a1cce8190710688b4f2f17b2850
parent9a567843f7ce0037bfd4d5fdc58a09d0a527b28b
md: don't set In_sync if array is frozen

When a disk is added to array, the following path is called in mdadm.

Manage_subdevs -> sysfs_freeze_array
               -> Manage_add
               -> sysfs_set_str(&info, NULL, "sync_action","idle")

Then from kernel side, Manage_add invokes the path (add_new_disk ->
validate_super = super_1_validate) to set In_sync flag.

Since In_sync means "device is in_sync with rest of array", and the new
added disk need to resync thread to help the synchronization of data.
And md_reap_sync_thread would call spare_active to set In_sync for the
new added disk finally. So don't set In_sync if array is in frozen.

Signed-off-by: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
Signed-off-by: Song Liu <songliubraving@fb.com>
drivers/md/md.c