On Fri, Jun 15, 2018 at 02:05:59PM +0300, Nikolay Borisov wrote: > To help implement free space tree checker in user space some kernel > function are necessary, namely iterating/deleting/adding freespace > items, some internal search functions. Functions to populate a block > group based on the extent tree. The code is largely copy/paste from > the kernel with locking eliminated (i.e free_space_lock). It supports > reading/writing of both bitmap and extent based FST trees. > > Signed-off-by: Nikolay Borisov <nborisov@xxxxxxxx> Why doesn't this include the bitmap <-> extent conversions? If we end up rebuilding the free space tree, we're never going to use the bitmap format, which sucks if the free space is fragmented.
