From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
To: Dongjiang Zhu <zhudongjiang@fygo.io>, linux-btrfs@vger.kernel.org
Cc: naohiro.aota@wdc.com
Subject: Re: [PATCH v2 1/4] btrfs: zoned: track only sequential zones as active
Date: Wed, 26 Aug 2026 11:00:43 +0200 [thread overview]
Message-ID: <e852d4c2-6765-4d8e-aaa4-f7dd1dc21163@wdc.com> (raw)
In-Reply-To: <c51aaf7f4621dedc36c275bfa9ba1ec884de09c4.1787717573.git.zhudongjiang@fygo.io>
On 8/26/26 6:27 AM, Dongjiang Zhu wrote:
> diff --git a/fs/btrfs/block-group.h b/fs/btrfs/block-group.h
> index 69d56864d4ba..37ab8b7eee9c 100644
> --- a/fs/btrfs/block-group.h
> +++ b/fs/btrfs/block-group.h
> @@ -80,13 +80,17 @@ enum btrfs_block_group_flags {
> BLOCK_GROUP_FLAG_TO_COPY,
> BLOCK_GROUP_FLAG_RELOCATING_REPAIR,
> BLOCK_GROUP_FLAG_CHUNK_ITEM_INSERTED,
> + /*
> + * Only block groups containing sequential zones can have this bit set;
> + * conventional-only block groups never do.
> + */
Again this comment does not really serve any purpose.
next prev parent reply other threads:[~2026-08-26 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 4:27 [PATCH v2 0/4] btrfs: zoned: fix active-zone accounting and transitions Dongjiang Zhu
2026-08-26 4:27 ` [PATCH v2 1/4] btrfs: zoned: track only sequential zones as active Dongjiang Zhu
2026-08-26 9:00 ` Johannes Thumshirn [this message]
2026-08-27 2:06 ` Dongjiang Zhu
2026-08-28 4:42 ` Naohiro Aota
2026-08-28 12:03 ` Dongjiang Zhu
2026-08-26 4:27 ` [PATCH v2 2/4] btrfs: zoned: recover active non-data block group roles on mount Dongjiang Zhu
2026-08-26 4:27 ` [PATCH v2 3/4] btrfs: zoned: remove obsolete non-data block group activation helper Dongjiang Zhu
2026-08-26 4:27 ` [PATCH v2 4/4] btrfs: zoned: serialize zone finishing per block group Dongjiang Zhu
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=e852d4c2-6765-4d8e-aaa4-f7dd1dc21163@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=zhudongjiang@fygo.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox