diff options
| author |   Anand Jain <anand.jain@oracle.com> | 2020-09-05 01:34:30 +0800 |
|---|---|---|
| committer |   David Sterba <dsterba@suse.com> | 2020-10-07 12:12:22 +0200 |
| commit | 2fca0db07608a303dbe9db802ecca678e358dca9 (patch) | |
| tree | 86eee6ef3563eb031520513468d6b2b8d91e4420 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | btrfs: handle errors in btrfs_sysfs_add_fs_devices (diff) | |
| download | wireguard-linux-2fca0db07608a303dbe9db802ecca678e358dca9.tar.xz wireguard-linux-2fca0db07608a303dbe9db802ecca678e358dca9.zip | |
btrfs: reada: lock all seed/sprout devices in __reada_start_machine
On an fs mounted using a sprout device, the seed fs_devices are
maintained in a linked list under fs_info->fs_devices. Each seeds
fs_devices also has device_list_mutex initialized to protect against the
potential race with delete threads. But the delete thread (at
btrfs_rm_device()) is holding the fs_info::fs_devices::device_list_mutex
mutex which belongs to sprout device_list_mutex instead of seed
device_list_mutex. Moreover, there aren't any significient benefits in
using the seed::device_list_mutex instead of sprout::device_list_mutex.
So this patch converts them of using the seed::device_list_mutex to
sprout::device_list_mutex.
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
Signed-off-by: Anand Jain <anand.jain@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions