summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/extent-io-tree.h
diff options
context:
space:
mode:
authorJosef Bacik <josef@toxicpanda.com>2022-09-09 17:53:17 -0400
committerDavid Sterba <dsterba@suse.com>2022-09-26 12:28:02 +0200
commitcdca85b092fbf4ce6f209b174ac3e7ef2b80bebf (patch)
tree3fd34bed404283eea8b8dacbe9c1cfe6843fb874 /fs/btrfs/extent-io-tree.h
parent87c11705cc94d6b822551e88d8d4579fe0370051 (diff)
downloadlinux-stable-cdca85b092fbf4ce6f209b174ac3e7ef2b80bebf.tar.gz
linux-stable-cdca85b092fbf4ce6f209b174ac3e7ef2b80bebf.tar.bz2
linux-stable-cdca85b092fbf4ce6f209b174ac3e7ef2b80bebf.zip
btrfs: use find_first_extent_bit in btrfs_clean_io_failure
Currently we're using find_first_extent_bit_state to check if our state contains the given failrec range, however this is more of an internal extent_io_tree helper, and is technically unsafe to use because we're accessing the state outside of the extent_io_tree lock. Instead use the normal helper find_first_extent_bit which returns the range of the extent state we find in find_first_extent_bit_state and use that to do our sanity checking. Signed-off-by: Josef Bacik <josef@toxicpanda.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/extent-io-tree.h')
0 files changed, 0 insertions, 0 deletions