public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, gality369@gmail.com
Subject: Re: [PATCH 1/2] btrfs: tree-checker: introduce checks for FREE_SPACE_INFO
Date: Fri, 13 Mar 2026 20:47:39 +0100	[thread overview]
Message-ID: <20260313194739.GL5735@twin.jikos.cz> (raw)
In-Reply-To: <dcc4425060fb18e7dc5b45e4ea05cd8afec13f6c.1773094579.git.wqu@suse.com>

On Tue, Mar 10, 2026 at 08:49:25AM +1030, Qu Wenruo wrote:
> Introduce checks for FREE_SPACE_INFO item, which include:
> 
> - Key alignment check
>   The objectid is the logical bytenr of the chunk/bg, and offset is the
>   length of the chunk/bg, thus they should all be aligned to the fs
>   block size.
> 
> - Item size check
>   The FREE_SPACE_INFO should a fix size.
> 
> - Flags check
>   The flags member should has no other flags than
>   BTRFS_FREE_SPACE_USING_BITMAPS.
> 
>   For future expansion, introduce a new macro
>   BTRFS_FREE_SPACE_FLAGS_MASK for such checks.
> 
>   And since we're here, the BTRFS_FREE_SPACE_USING_BITMAPS should not
>   use unsigned long long, as the flags is only 32 bits wide.
>   So fix that to use unsigned long.
> 
> - Extent count check
>   That member shows how many free space bitmap/extent items there are
>   inside the chunk/bg.
> 
>   And we know the chunk size (from key->offset), thus there should be at
>   most (key->offset >> sectorsize_bits) blocks inside the chunk.
>   Use that value as the upper limit and if that counter is larger than
>   that, there is a high chance it's a bitflip in high bits.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
>  fs/btrfs/tree-checker.c         | 45 +++++++++++++++++++++++++++++++++
>  include/uapi/linux/btrfs_tree.h |  3 ++-
>  2 files changed, 47 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/tree-checker.c b/fs/btrfs/tree-checker.c
> index ac4c4573ee39..980e4d52061f 100644
> --- a/fs/btrfs/tree-checker.c
> +++ b/fs/btrfs/tree-checker.c
> @@ -1928,6 +1928,48 @@ static int check_dev_extent_item(const struct extent_buffer *leaf,
>  	return 0;
>  }
>  
> +static int check_free_space_info(struct extent_buffer *leaf, struct btrfs_key *key,
> +				 int slot)
> +{
> +	struct btrfs_fs_info *fs_info = leaf->fs_info;
> +	struct btrfs_free_space_info *fsi;
> +	const u32 blocksize = fs_info->sectorsize;
> +	u32 flags;
> +
> +	if (unlikely(!IS_ALIGNED(key->objectid, blocksize) ||
> +		     !IS_ALIGNED(key->offset, blocksize))) {
> +		generic_err(leaf, slot,
> +		"free space info key range is not aligned to %u, has (%llu %u %llu)",

Please use the BTRFS_KEY_FMT macro for key specifier, I'll fix it in
git, thanks.

  parent reply	other threads:[~2026-03-13 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 22:19 [PATCH 0/2] btrfs: add free space tree checks except for FREE_SPACE_BITMAP Qu Wenruo
2026-03-09 22:19 ` [PATCH 1/2] btrfs: tree-checker: introduce checks for FREE_SPACE_INFO Qu Wenruo
2026-03-10 10:36   ` Johannes Thumshirn
2026-03-13 19:47   ` David Sterba [this message]
2026-03-09 22:19 ` [PATCH 2/2] btrfs: tree-checker: introduce checks for FREE_SPACE_EXTENT Qu Wenruo
2026-03-10 10:41   ` Johannes Thumshirn
2026-03-10 10:42 ` [PATCH 0/2] btrfs: add free space tree checks except for FREE_SPACE_BITMAP 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=20260313194739.GL5735@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=gality369@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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