History

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.

NeilBrown committed 11 years ago

Commit 8e8e2511 parent c008f1d1 file · +6 −5Browse files

Unified · Split

drivers/md/md.c+6−5
@@ -4217,13 +4217,14 @@ action_store(struct mddev *mddev, const char *page, size_t len) · 4216 unmodified lines
42174217 set_bit(MD_RECOVERY_FROZEN, &mddev->recovery);
42184218 else
42194219 clear_bit(MD_RECOVERY_FROZEN, &mddev->recovery);
4220− flush_workqueue(md_misc_wq);
4221− if (mddev->sync_thread) {
4222− set_bit(MD_RECOVERY_INTR, &mddev->recovery);
4223− if (mddev_lock(mddev) == 0) {
4220+ if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) &&
4221+ mddev_lock(mddev) == 0) {
4222+ flush_workqueue(md_misc_wq);
4223+ if (mddev->sync_thread) {
4224+ set_bit(MD_RECOVERY_INTR, &mddev->recovery);
42244225 md_reap_sync_thread(mddev);
4225− mddev_unlock(mddev);
42264226 }
4227+ mddev_unlock(mddev);
42274228 }
42284229 } else if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) ||
42294230 test_bit(MD_RECOVERY_NEEDED, &mddev->recovery))

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t