Re: [PATCH 4/8] btrfs: Remove extent_io_ops::check_extent_io_range callback

2018-11-01 Thread Josef Bacik
On Thu, Nov 01, 2018 at 02:09:49PM +0200, Nikolay Borisov wrote: > This callback was only used in debug builds by btrfs_leak_debug_check. > A better approach is to move its implementation in > btrfs_leak_debug_check and ensure the latter is only executed for > extent tree which have ->private_data

[PATCH 4/8] btrfs: Remove extent_io_ops::check_extent_io_range callback

2018-11-01 Thread Nikolay Borisov
This callback was only used in debug builds by btrfs_leak_debug_check. A better approach is to move its implementation in btrfs_leak_debug_check and ensure the latter is only executed for extent tree which have ->private_data set i.e. relate to a data node and not the btree one. No functional