From: "Miquel Sabaté Solà" <mssola@mssola.com>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: zoned: reset active_meta_bg on zone finish
Date: Fri, 03 Jul 2026 11:31:24 +0200 [thread overview]
Message-ID: <87y0fs772r.fsf@> (raw)
In-Reply-To: <20260703084559.136605-1-johannes.thumshirn@wdc.com> (Johannes Thumshirn's message of "Fri, 3 Jul 2026 10:45:59 +0200")
[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]
Hi,
If you don't mind, a couple of questions from a newcomer that is trying
to grok this part of the code :)
Johannes Thumshirn @ 2026-07-03 10:45 +02:
> do_zone_finish() clears BLOCK_GROUP_FLAG_ZONE_IS_ACTIVE and removes the
> block group from zone_active_bgs, but only the path in
> check_bg_is_active() resets fs_info->active_meta_bg / active_system_bg.
> Any other finish path leaves active_meta_bg / active_system_bg pointing
> at an inactive, fully written block group.
>
> Reset the corresponding active_{meta,system}_bg pointer in do_zone_finish()
> so it can never go stale.
>
> Fixes: 13bb483d32ab ("btrfs: zoned: activate metadata block group on write time")
> Cc: stable@vger.kernel.org
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> ---
> fs/btrfs/zoned.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
> index 44a13ed6b8b2..c8c850de1702 100644
> --- a/fs/btrfs/zoned.c
> +++ b/fs/btrfs/zoned.c
> @@ -2539,6 +2539,7 @@ static int do_zone_finish(struct btrfs_block_group *block_group, bool fully_writ
> const bool is_metadata = (block_group->flags &
> (BTRFS_BLOCK_GROUP_METADATA | BTRFS_BLOCK_GROUP_SYSTEM));
> struct btrfs_dev_replace *dev_replace = &fs_info->dev_replace;
> + struct btrfs_block_group **active_bg = NULL;
> int ret = 0;
> int i;
>
> @@ -2636,6 +2637,20 @@ static int do_zone_finish(struct btrfs_block_group *block_group, bool fully_writ
> /* For active_bg_list */
> btrfs_put_block_group(block_group);
>
> + if (block_group->flags & BTRFS_BLOCK_GROUP_SYSTEM)
> + active_bg = &fs_info->active_system_bg;
> + else if (block_group->flags & BTRFS_BLOCK_GROUP_METADATA)
> + active_bg = &fs_info->active_meta_bg;
> +
> + if (active_bg) {
> + btrfs_zoned_meta_io_lock(fs_info);
If you need to lock/unlock in order call btrfs_put_block_group() and
then reset *active_bg, couldn't the previous if statement be written
like so?
if (active_bg && (*active_bg == block_group)) {
This would then only lock/unlock just in the case we really want to
touch this 'block_group', no?
> + if (*active_bg == block_group) {
> + btrfs_put_block_group(block_group);
Also, hasn't 'block_group' already been put before your patch? Won't
this try to double-free this pointer? Or it is about decreasing the
reference twice for this block group?
> + *active_bg = NULL;
> + }
> + btrfs_zoned_meta_io_unlock(fs_info);
> + }
> +
> clear_and_wake_up_bit(BTRFS_FS_NEED_ZONE_FINISH, &fs_info->flags);
>
> return 0;
Thanks,
Miquel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 897 bytes --]
next prev parent reply other threads:[~2026-07-03 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 8:45 [PATCH] btrfs: zoned: reset active_meta_bg on zone finish Johannes Thumshirn
2026-07-03 9:31 ` Miquel Sabaté Solà [this message]
2026-07-03 9:50 ` Johannes Thumshirn
2026-07-03 11:41 ` Miquel Sabaté Solà
2026-07-03 11:51 ` Johannes Thumshirn
2026-07-03 10:01 ` Johannes Thumshirn
2026-07-03 11:46 ` Miquel Sabaté Solà
2026-07-03 11:50 ` Johannes Thumshirn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y0fs772r.fsf@ \
--to=mssola@mssola.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.