summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid5.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2015-06-12 11:51:27 +0200
committerNeilBrown <neilb@suse.de>2015-06-12 12:16:26 +0200
commit8e8e2518fceca407bb8fc2a6710d19d2e217892e (patch)
treec4218aeaeac0d11dd2c34652a0a947bb157f81d7 /drivers/md/raid5.c
parentmd: don't return 0 from array_state_store (diff)
downloadlinux-8e8e2518fceca407bb8fc2a6710d19d2e217892e.tar.xz
linux-8e8e2518fceca407bb8fc2a6710d19d2e217892e.zip
md: Close race when setting 'action' to 'idle'.
Checking ->sync_thread without holding the mddev_lock() isn't really safe, even after flushing the workqueue which ensures md_start_sync() has been run. While this code is waiting for the lock, md_check_recovery could reap the thread itself, and then start another thread (e.g. recovery might finish, then reshape starts). When this thread gets the lock md_start_sync() hasn't run so it doesn't get reaped, but MD_RECOVERY_RUNNING gets cleared. This allows two threads to start which leads to confusion. So don't both if MD_RECOVERY_RUNNING isn't set, but if it is do the flush and the test and the reap all under the mddev_lock to avoid any race with md_check_recovery. Signed-off-by: NeilBrown <neilb@suse.de> Fixes: 6791875e2e53 ("md: make reconfig_mutex optional for writes to md sysfs files.") Cc: stable@vger.kernel.org (v4.0+)
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions