summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorJohannes Thumshirn <johannes.thumshirn@wdc.com>2026-08-24 18:19:10 +0200
committerDavid Sterba <dsterba@suse.com>2026-09-14 21:59:50 +0200
commit3a35e787ac1acf94d33eebb26fd7248811cc66c9 (patch)
tree7457efc77db6ac922bf5ea4e57523bd17c98db2f /tools/perf/scripts/python/bin
parent09f1294ee2abee7fe1c2d600671498b7642e0fe0 (diff)
downloadlinux-next-3a35e787ac1acf94d33eebb26fd7248811cc66c9.tar.gz
linux-next-3a35e787ac1acf94d33eebb26fd7248811cc66c9.zip
btrfs: zoned: handle RAID profiles in btrfs_can_activate_zone()
btrfs_can_activate_zone() only accounts for the single and DUP profiles. For a RAID0, RAID1, RAID1C3, RAID1C4 or RAID10 block group the profile switch matches no case, so 'ret' stays false and the function reports that no zone can be activated, even when the devices have plenty of active zones left. As a side effect BTRFS_FS_NEED_ZONE_FINISH gets set and, since btrfs_can_activate_zone() bails out early once that bit is set, data allocations will fail permanently: writers loop on -EAGAIN and hang in btrfs_new_extent_direct() waiting for the bit to clear. Each of these profiles needs one active zone per device, just like single, so handle them the same way. Reviewed-by: Boris Burkov <boris@bur.io> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions