diff options
| author | Josef Bacik <[email protected]> | 2022-09-09 21:53:43 +0000 |
|---|---|---|
| committer | David Sterba <[email protected]> | 2022-09-26 10:28:05 +0000 |
| commit | 570eb97bace8743f45c6830b64c7a0889d0915dd (patch) | |
| tree | dd6e39e3006b7a4c91abe461074e9fed4e2aa559 /fs/btrfs/extent-io-tree.c | |
| parent | btrfs: drop extent_changeset from set_extent_bit (diff) | |
| download | kernel-570eb97bace8743f45c6830b64c7a0889d0915dd.tar.gz kernel-570eb97bace8743f45c6830b64c7a0889d0915dd.zip | |
btrfs: unify the lock/unlock extent variants
We have two variants of lock/unlock extent, one set that takes a cached
state, another that does not. This is slightly annoying, and generally
speaking there are only a few places where we don't have a cached state.
Simplify this by making lock_extent/unlock_extent the only variant and
make it take a cached state, then convert all the callers appropriately.
Signed-off-by: Josef Bacik <[email protected]>
Reviewed-by: David Sterba <[email protected]>
Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'fs/btrfs/extent-io-tree.c')
| -rw-r--r-- | fs/btrfs/extent-io-tree.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/btrfs/extent-io-tree.c b/fs/btrfs/extent-io-tree.c index de5f54c2f543..02e9eda59cb7 100644 --- a/fs/btrfs/extent-io-tree.c +++ b/fs/btrfs/extent-io-tree.c @@ -1649,8 +1649,8 @@ int try_lock_extent(struct extent_io_tree *tree, u64 start, u64 end) * Either insert or lock state struct between start and end use mask to tell * us if waiting is desired. */ -int lock_extent_bits(struct extent_io_tree *tree, u64 start, u64 end, - struct extent_state **cached_state) +int lock_extent(struct extent_io_tree *tree, u64 start, u64 end, + struct extent_state **cached_state) { int err; u64 failed_start; |