From: Qu Wenruo <wqu@suse.com>
To: ZhengYuan Huang <gality369@gmail.com>, dsterba@suse.com, clm@fb.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: tree-checker: fix misleading root drop_level error message
Date: Thu, 12 Mar 2026 11:38:25 +1030 [thread overview]
Message-ID: <fb3948bf-1000-4626-b27c-90cd011bc495@suse.com> (raw)
In-Reply-To: <20260312003321.3019495-1-gality369@gmail.com>
在 2026/3/12 11:03, ZhengYuan Huang 写道:
> Fix tree-checker error message to report "invalid root drop_level"
> instead of the misleading "invalid root level".
>
> Fixes: 259ee7754b67 ("btrfs: tree-checker: Add ROOT_ITEM check")
> Signed-off-by: ZhengYuan Huang <gality369@gmail.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> [CHANGELOG]
> v2:
> - Split out the error message fix from the previous patch, as requested
> during review.
> ---
> fs/btrfs/tree-checker.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/tree-checker.c b/fs/btrfs/tree-checker.c
> index 1e052c3303b3..a8c568b10432 100644
> --- a/fs/btrfs/tree-checker.c
> +++ b/fs/btrfs/tree-checker.c
> @@ -1256,7 +1256,7 @@ static int check_root_item(struct extent_buffer *leaf, struct btrfs_key *key,
> }
> if (unlikely(btrfs_root_drop_level(&ri) >= BTRFS_MAX_LEVEL)) {
> generic_err(leaf, slot,
> - "invalid root level, have %u expect [0, %u]",
> + "invalid root drop_level, have %u expect [0, %u]",
> btrfs_root_drop_level(&ri), BTRFS_MAX_LEVEL - 1);
> return -EUCLEAN;
> }
prev parent reply other threads:[~2026-03-12 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 0:33 [PATCH v2] btrfs: tree-checker: fix misleading root drop_level error message ZhengYuan Huang
2026-03-12 1:08 ` Qu Wenruo [this message]
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=fb3948bf-1000-4626-b27c-90cd011bc495@suse.com \
--to=wqu@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=gality369@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox