btrfs: zoned: remove max_zone_append_size logic
authorJohannes Thumshirn <johannes.thumshirn@wdc.com>
Mon, 28 Jun 2021 18:36:45 +0000 (03:36 +0900)
committerDavid Sterba <dsterba@suse.com>
Mon, 23 Aug 2021 11:18:58 +0000 (13:18 +0200)
commit5a80d1c6a2704d880c1df30315a1d9b0dc1f2cd8
tree2cb402b38faaa459309a18f20ff101bb396162f3
parente22ce8eb631bdc47a4a4ea7ecf4e4ba499db4f93
btrfs: zoned: remove max_zone_append_size logic

There used to be a patch in the original series for zoned support which
limited the extent size to max_zone_append_size, but this patch has been
dropped somewhere around v9.

We've decided to go the opposite direction, instead of limiting extents
in the first place we split them before submission to comply with the
device's limits.

Remove the related code, btrfs_fs_info::max_zone_append_size and
btrfs_zoned_device_info::max_zone_append_size.

This also removes the workaround for dm-crypt introduced in
1d68128c107a ("btrfs: zoned: fail mount if the device does not support
zone append") because the fix has been merged as f34ee1dce642 ("dm
crypt: Fix zoned block device support").

Reviewed-by: Anand Jain <anand.jain@oracle.com>
Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/ctree.h
fs/btrfs/extent_io.c
fs/btrfs/zoned.c
fs/btrfs/zoned.h