Nikolay Borisov 1eaebb341d btrfs: Don't trim returned range based on input value in find_first_clear_extent_bit ... Currently find_first_clear_extent_bit always returns a range whose starting value is >= passed 'start'. This implicit trimming behavior is somewhat subtle and an implementation detail. Instead, this patch modifies the function such that now it always returns the range which contains passed 'start' and has the given bits unset. This range could either be due to presence of existing records which contains 'start' but have the bits unset or because there are no records that contain the given starting offset. This patch also adds test cases which cover find_first_clear_extent_bit since they were missing up until now. Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Nikolay Borisov <nborisov@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>		2019-07-01 13:35:02 +02:00
..
btrfs-tests.c	btrfs: qgroup: remove obsolete fs_info members	2019-04-29 19:02:31 +02:00
btrfs-tests.h	btrfs: tests: add table of most common errors	2019-04-29 19:02:25 +02:00
extent-buffer-tests.c	btrfs: tests: use standard error message after path allocation failure	2019-04-29 19:02:26 +02:00
extent-io-tests.c	btrfs: Don't trim returned range based on input value in find_first_clear_extent_bit	2019-07-01 13:35:02 +02:00
extent-map-tests.c	btrfs: tests: fix comments about tested extent map ranges	2019-04-29 19:02:28 +02:00
free-space-tests.c	btrfs: tests: unify messages when tests start	2019-04-29 19:02:28 +02:00
free-space-tree-tests.c	for-5.2-tag	2019-05-07 11:34:19 -07:00
inode-tests.c	btrfs: inode: Verify inode mode to avoid NULL pointer dereference	2019-04-29 19:02:32 +02:00
qgroup-tests.c	btrfs: tests: unify messages when tests start	2019-04-29 19:02:28 +02:00