btrfs: zoned: do not zone finish data relocation block group

When multiple writes happen at once, we may need to sacrifice a currently
active block group to be zone finished for a new allocation. We choose a
block group with the least free space left, and zone finish it.

To do the finishing, we need to send IOs for already allocated region
and wait for them and on-going IOs. Otherwise, these IOs fail because the
zone is already finished at the time the IO reach a device.

However, if a block group dedicated to the data relocation is zone
finished, there is a chance that finishing it before an ongoing write IO
reaches the device. That is because there is timing gap between an
allocation is done (block_group->reservations == 0, as pre-allocation is
done) and an ordered extent is created when the relocation IO starts.
Thus, if we finish the zone between them, we can fail the IOs.

We cannot simply use "fs_info->data_reloc_bg == block_group->start" to
avoid the zone finishing. Because, the data_reloc_bg may already switch to
a new block group, while there are still ongoing write IOs to the old
data_reloc_bg.

So, this patch reworks the BLOCK_GROUP_FLAG_ZONED_DATA_RELOC bit to
indicate there is a data relocation allocation and/or ongoing write to the
block group. The bit is set on allocation and cleared in end_io function of
the last IO for the currently allocated region.

To change the timing of the bit setting also solves the issue that the bit
being left even after there is no IO going on. With the current code, if
the data_reloc_bg switches after the last IO to the current data_reloc_bg,
the bit is set at this timing and there is no one clearing that bit. As a
result, that block group is kept unallocatable for anything.

Fixes: 343d8a30851c ("btrfs: zoned: prevent allocation from previous data relocation BG")
Fixes: 74e91b12b115 ("btrfs: zoned: zone finish unused block group")
CC: stable@vger.kernel.org # 6.1+
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Signed-off-by: David Sterba <dsterba@suse.com>

diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index ba22790..e050811 100644 (file)
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -3738,7 +3738,8 @@ static int do_allocation_zoned(struct btrfs_block_group *block_group,
               fs_info->data_reloc_bg == 0);
 
        if (block_group->ro ||
-           test_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC, &block_group->runtime_flags)) {
+           (!ffe_ctl->for_data_reloc &&
+            test_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC, &block_group->runtime_flags))) {
                ret = 1;
                goto out;
        }
@@ -3781,8 +3782,26 @@ static int do_allocation_zoned(struct btrfs_block_group *block_group,
        if (ffe_ctl->for_treelog && !fs_info->treelog_bg)
                fs_info->treelog_bg = block_group->start;
 
-       if (ffe_ctl->for_data_reloc && !fs_info->data_reloc_bg)
-               fs_info->data_reloc_bg = block_group->start;
+       if (ffe_ctl->for_data_reloc) {
+               if (!fs_info->data_reloc_bg)
+                       fs_info->data_reloc_bg = block_group->start;
+               /*
+                * Do not allow allocations from this block group, unless it is
+                * for data relocation. Compared to increasing the ->ro, setting
+                * the ->zoned_data_reloc_ongoing flag still allows nocow
+                * writers to come in. See btrfs_inc_nocow_writers().
+                *
+                * We need to disable an allocation to avoid an allocation of
+                * regular (non-relocation data) extent. With mix of relocation
+                * extents and regular extents, we can dispatch WRITE commands
+                * (for relocation extents) and ZONE APPEND commands (for
+                * regular extents) at the same time to the same zone, which
+                * easily break the write pointer.
+                *
+                * Also, this flag avoids this block group to be zone finished.
+                */
+               set_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC, &block_group->runtime_flags);
+       }
 
        ffe_ctl->found_offset = start + block_group->alloc_offset;
        block_group->alloc_offset += num_bytes;
@@ -3800,24 +3819,8 @@ static int do_allocation_zoned(struct btrfs_block_group *block_group,
 out:
        if (ret && ffe_ctl->for_treelog)
                fs_info->treelog_bg = 0;
-       if (ret && ffe_ctl->for_data_reloc &&
-           fs_info->data_reloc_bg == block_group->start) {
-               /*
-                * Do not allow further allocations from this block group.
-                * Compared to increasing the ->ro, setting the
-                * ->zoned_data_reloc_ongoing flag still allows nocow
-                *  writers to come in. See btrfs_inc_nocow_writers().
-                *
-                * We need to disable an allocation to avoid an allocation of
-                * regular (non-relocation data) extent. With mix of relocation
-                * extents and regular extents, we can dispatch WRITE commands
-                * (for relocation extents) and ZONE APPEND commands (for
-                * regular extents) at the same time to the same zone, which
-                * easily break the write pointer.
-                */
-               set_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC, &block_group->runtime_flags);
+       if (ret && ffe_ctl->for_data_reloc)
                fs_info->data_reloc_bg = 0;
-       }
        spin_unlock(&fs_info->relocation_bg_lock);
        spin_unlock(&fs_info->treelog_bg_lock);
        spin_unlock(&block_group->lock);

diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
index 52f49b0..a2f8e74 100644 (file)
--- a/fs/btrfs/zoned.c
+++ b/fs/btrfs/zoned.c
@@ -2091,6 +2091,10 @@ static int do_zone_finish(struct btrfs_block_group *block_group, bool fully_writ
         * and block_group->meta_write_pointer for metadata.
         */
        if (!fully_written) {
+               if (test_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC, &block_group->runtime_flags)) {
+                       spin_unlock(&block_group->lock);
+                       return -EAGAIN;
+               }
                spin_unlock(&block_group->lock);
 
                ret = btrfs_inc_block_group_ro(block_group, false);
@@ -2119,7 +2123,9 @@ static int do_zone_finish(struct btrfs_block_group *block_group, bool fully_writ
                        return 0;
                }
 
-               if (block_group->reserved) {
+               if (block_group->reserved ||
+                   test_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC,
+                            &block_group->runtime_flags)) {
                        spin_unlock(&block_group->lock);
                        btrfs_dec_block_group_ro(block_group);
                        return -EAGAIN;
@@ -2362,7 +2368,10 @@ void btrfs_zoned_release_data_reloc_bg(struct btrfs_fs_info *fs_info, u64 logica
 
        /* All relocation extents are written. */
        if (block_group->start + block_group->alloc_offset == logical + length) {
-               /* Now, release this block group for further allocations. */
+               /*
+                * Now, release this block group for further allocations and
+                * zone finish.
+                */
                clear_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC,
                          &block_group->runtime_flags);
        }
@@ -2386,7 +2395,8 @@ int btrfs_zone_finish_one_bg(struct btrfs_fs_info *fs_info)
 
                spin_lock(&block_group->lock);
                if (block_group->reserved || block_group->alloc_offset == 0 ||
-                   (block_group->flags & BTRFS_BLOCK_GROUP_SYSTEM)) {
+                   (block_group->flags & BTRFS_BLOCK_GROUP_SYSTEM) ||
+                   test_bit(BLOCK_GROUP_FLAG_ZONED_DATA_RELOC, &block_group->runtime_flags)) {
                        spin_unlock(&block_group->lock);
                        continue;
                }