public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mark Harmstone <mark@harmstone.com>,
	linux-btrfs@vger.kernel.org, wqu@suse.com
Subject: Re: [PATCH] btrfs: fix chunk offset error message in check_dev_extent_item()
Date: Sat, 21 Feb 2026 07:11:50 +1030	[thread overview]
Message-ID: <6ea99497-10bb-40a1-9432-11c59cdf3fcd@gmx.com> (raw)
In-Reply-To: <20260220113013.30254-1-mark@harmstone.com>



在 2026/2/20 22:00, Mark Harmstone 写道:
> Fix a copy-paste bug in an error message in check_dev_extent_item():
> we're reporting an incorrect offset, but actually printing the objectid.
> 
> Signed-off-by: Mark Harmstone <mark@harmstone.com>
> Fixes: 008e2512dc56 ("btrfs: tree-checker: add dev extent item checks")

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> ---
>   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 ac4c4573ee39..133510f99fc5 100644
> --- a/fs/btrfs/tree-checker.c
> +++ b/fs/btrfs/tree-checker.c
> @@ -1899,7 +1899,7 @@ static int check_dev_extent_item(const struct extent_buffer *leaf,
>   				 sectorsize))) {
>   		generic_err(leaf, slot,
>   			    "invalid dev extent chunk offset, has %llu not aligned to %u",
> -			    btrfs_dev_extent_chunk_objectid(leaf, de),
> +			    btrfs_dev_extent_chunk_offset(leaf, de),
>   			    sectorsize);
>   		return -EUCLEAN;
>   	}


      reply	other threads:[~2026-02-20 20:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 11:30 [PATCH] btrfs: fix chunk offset error message in check_dev_extent_item() Mark Harmstone
2026-02-20 20:41 ` 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=6ea99497-10bb-40a1-9432-11c59cdf3fcd@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mark@harmstone.com \
    --cc=wqu@suse.com \
    /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