Commit 7034674
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>1 parent 0586d0a commit 7034674
1 file changed
Lines changed: 7 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
742 | 742 | | |
743 | 743 | | |
744 | 744 | | |
745 | | - | |
| 745 | + | |
746 | 746 | | |
747 | 747 | | |
748 | | - | |
| 748 | + | |
749 | 749 | | |
750 | 750 | | |
751 | 751 | | |
| |||
755 | 755 | | |
756 | 756 | | |
757 | 757 | | |
758 | | - | |
759 | | - | |
760 | | - | |
761 | 758 | | |
762 | 759 | | |
763 | 760 | | |
| |||
1031 | 1028 | | |
1032 | 1029 | | |
1033 | 1030 | | |
| 1031 | + | |
1034 | 1032 | | |
1035 | 1033 | | |
1036 | | - | |
1037 | | - | |
| 1034 | + | |
1038 | 1035 | | |
1039 | 1036 | | |
1040 | | - | |
| 1037 | + | |
1041 | 1038 | | |
1042 | 1039 | | |
1043 | 1040 | | |
1044 | 1041 | | |
1045 | 1042 | | |
| 1043 | + | |
1046 | 1044 | | |
1047 | 1045 | | |
1048 | 1046 | | |
| |||
1352 | 1350 | | |
1353 | 1351 | | |
1354 | 1352 | | |
1355 | | - | |
1356 | | - | |
| 1353 | + | |
1357 | 1354 | | |
1358 | 1355 | | |
1359 | 1356 | | |
| |||
0 commit comments