btrfs: fix bytes_may_use leak in move_existing_remap()

If the call to btrfs_reserve_extent() in move_existing_remap() returns a
smaller extent than we asked for, currently we're not undoing the
bytes_may_use change that we made. Fix this by calling
btrfs_space_info_update_bytes_may_use() again for the difference.

Fixes: bbea42dfb9 ("btrfs: move existing remaps before relocating block group")
Reviewed-by: Boris Burkov <boris@bur.io>
Signed-off-by: Mark Harmstone <mark@harmstone.com>
Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
Mark Harmstone 2026-03-23 12:59:47 +00:00 committed by David Sterba
parent fc3d532881
commit 68a135013b

View File

@ -4174,6 +4174,12 @@ static int move_existing_remap(struct btrfs_fs_info *fs_info,
return ret;
}
if (ins.offset < length) {
spin_lock(&sinfo->lock);
btrfs_space_info_update_bytes_may_use(sinfo, ins.offset - length);
spin_unlock(&sinfo->lock);
}
dest_addr = ins.objectid;
dest_length = ins.offset;