diff options
| author | Filipe Manana <fdmanana@suse.com> | 2026-10-05 13:19:41 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2026-10-12 19:16:25 +0200 |
| commit | bbb86c6dc1a8168c4f718b246dc0857321c7ba81 (patch) | |
| tree | 6c1b379bea90437053012c289994ff859f8fd019 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | c97b139c6ceeb69b264e0a87f2a47bab651a51a8 (diff) | |
| download | linux-bbb86c6dc1a8168c4f718b246dc0857321c7ba81.tar.gz linux-bbb86c6dc1a8168c4f718b246dc0857321c7ba81.zip | |
btrfs: use READ_ONCE() to read the chunk size from the data space_info
The chunk size of a space_info is always updated with WRITE_ONCE() (see
btrfs_update_space_info_chunk_size()), so when reading it in
calc_effective_data_chunk_size() we should use READ_ONCE() to prevent
load tearing. We are already using READ_ONCE() in every other function
that accesses the chunk size of a space_info.
Reviewed-by: Daniel Vacek <neelx@suse.com>
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
