diff options
author | 2023-11-25 16:16:00 +0800 | |
---|---|---|
committer | 2023-11-27 15:49:04 -0800 | |
commit | c891f1fd90e66e584bb1353e1859cef7c9eb36f8 (patch) | |
tree | 564d8541ff7bc4be1145f85bb0ef194c833ea587 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" (diff) | |
download | wireguard-linux-c891f1fd90e66e584bb1353e1859cef7c9eb36f8.tar.xz wireguard-linux-c891f1fd90e66e584bb1353e1859cef7c9eb36f8.zip |
md: remove flag RemoveSynchronized
rcu is not used correctly here, because synchronize_rcu() is called
before replacing old value, for example:
remove_and_add_spares // other path
synchronize_rcu
// called before replacing old value
set_bit(RemoveSynchronized)
rcu_read_lock()
rdev = conf->mirros[].rdev
pers->hot_remove_disk
conf->mirros[].rdev = NULL;
if (!test_bit(RemoveSynchronized))
synchronize_rcu
/*
* won't be called, and won't wait
* for concurrent readers to be done.
*/
// access rdev after remove_and_add_spares()
rcu_read_unlock()
Fortunately, there is a separate rcu protection to prevent such rdev
to be freed:
md_kick_rdev_from_array //other path
rcu_read_lock()
rdev = conf->mirros[].rdev
list_del_rcu(&rdev->same_set)
rcu_read_unlock()
/*
* rdev can be removed from conf, but
* rdev won't be freed.
*/
synchronize_rcu()
free rdev
Hence remove this useless flag and prepare to remove rcu protection to
access rdev from 'conf'.
Signed-off-by: Yu Kuai <yukuai3@huawei.com>
Signed-off-by: Song Liu <song@kernel.org>
Link: https://lore.kernel.org/r/20231125081604.3939938-2-yukuai1@huaweicloud.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions