diff options
author | Josef Bacik <josef@toxicpanda.com> | 2024-04-03 20:42:45 +0300 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2024-05-07 22:31:09 +0300 |
commit | 7034674b8a070361b3149fdae377f5b80d5f860f (patch) | |
tree | 9415b2225e14a1df716170fc071817e07bb1afe4 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 0586d0a89e77d717da14df42648ace4a9fd67981 (diff) | |
download | linux-7034674b8a070361b3149fdae377f5b80d5f860f.tar.xz |
btrfs: lock extent when doing inline extent in compression
We currently don't lock the extent when we're doing a
cow_file_range_inline() for a compressed extent. This isn't a problem
necessarily, but it's inconsistent with the rest of our usage of
cow_file_range_inline(). This also leads to some extra weird logic
around whether the extent is locked or not. Fix this to lock the extent
before calling cow_file_range_inline() in compression to make it
consistent with the rest of the inline users. In future patches this
will be pushed down into the cow_file_range_inline() helper, so we're
fine with the quick and dirty locking here. This patch exists to make
the behavior change obvious.
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions