summaryrefslogtreecommitdiffstats
path: root/fs/compat_binfmt_elf.c
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2020-06-09 12:19:33 +0200
committerDavid Sterba <dsterba@suse.com>2020-07-27 12:55:21 +0200
commit46d4dac888ebe083d61f18acb16a6988e9062268 (patch)
tree243dce5cf88ca2fd4ef856855f46c63f523e618c /fs/compat_binfmt_elf.c
parentbtrfs: check-integrity: remove unnecessary failure messages during memory all... (diff)
downloadlinux-46d4dac888ebe083d61f18acb16a6988e9062268.tar.xz
linux-46d4dac888ebe083d61f18acb16a6988e9062268.zip
btrfs: remove the start argument from btrfs_free_reserved_data_space_noquota()
The start argument for btrfs_free_reserved_data_space_noquota() is only used to make sure the amount of bytes we decrement from the bytes_may_use counter of the data space_info object is aligned to the filesystem's sector size. It serves no other purpose. All its current callers always pass a length argument that is already aligned to the sector size, so we can make the start argument go away. In fact its presence makes it impossible to use it in a context where we just want to free a number of bytes for a range for which either we do not know its start offset or for freeing multiple ranges at once (which are not contiguous). This change is preparatory work for a patch (third patch in this series) that makes relocation of data block groups that are not full reserve less data space. Reviewed-by: Anand Jain <anand.jain@oracle.com> Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/compat_binfmt_elf.c')
0 files changed, 0 insertions, 0 deletions