linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: tree-checker: Add check for INODE_REF
Date: Mon, 26 Aug 2019 14:45:25 +0300	[thread overview]
Message-ID: <4c9195c9-5fc1-8524-e7d8-78ad1e942df7@suse.com> (raw)
In-Reply-To: <20190826074039.28517-3-wqu@suse.com>



On 26.08.19 г. 10:40 ч., Qu Wenruo wrote:
> For INODE_REF we will check:
> - Objectid (ino) against previous key
>   To detect missing INODE_ITEM.
> 
> - No overflow/padding in the data payload
>   Much like DIR_ITEM, but with less members to check.
> 
> Signed-off-by: Qu Wenruo <wqu@suse.com>
> ---
>  fs/btrfs/tree-checker.c | 53 +++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 53 insertions(+)
> 
> diff --git a/fs/btrfs/tree-checker.c b/fs/btrfs/tree-checker.c
> index 636ce1b4566e..3ce447eb591c 100644
> --- a/fs/btrfs/tree-checker.c
> +++ b/fs/btrfs/tree-checker.c
> @@ -842,6 +842,56 @@ static int check_inode_item(struct extent_buffer *leaf,
>  	return 0;
>  }
>  
> +#define inode_ref_err(fs_info, eb, slot, fmt, ...)		\
> +	inode_item_err(fs_info, eb, slot, fmt, __VA_ARGS__)

This define doesn't bring anything, just opencode the call to
inode_item_err directly.

> +static int check_inode_ref(struct extent_buffer *leaf,
> +			   struct btrfs_key *key, struct btrfs_key *prev_key,
> +			   int slot)
> +{
> +	struct btrfs_inode_ref *iref;
> +	unsigned long ptr;
> +	unsigned long end;
> +
> +	/* namelen can't be 0, so item_size == sizeof() is also invalid */
> +	if (btrfs_item_size_nr(leaf, slot) <= sizeof(*iref)) {
> +		inode_ref_err(fs_info, leaf, slot,
> +		"invalid item size, have %u expect (%zu, %u)",
> +			btrfs_item_size_nr(leaf, slot),
> +			sizeof(*iref), BTRFS_LEAF_DATA_SIZE(leaf->fs_info));
> +		return -EUCLEAN;
> +	}
> +
> +	ptr = btrfs_item_ptr_offset(leaf, slot);
> +	end = ptr + btrfs_item_size_nr(leaf, slot);
> +	while (ptr < end) {
> +		u16 namelen;
> +
> +		if (ptr + sizeof(iref) > end) {
> +			inode_ref_err(fs_info, leaf, slot,
> +		"inode ref overflow, ptr %lu end %lu inode_ref_size %zu",
> +				ptr, end, sizeof(iref));
> +			return -EUCLEAN;
> +		}
> +
> +		iref = (struct btrfs_inode_ref *)ptr;
> +		namelen = btrfs_inode_ref_name_len(leaf, iref);
> +		if (ptr + sizeof(*iref) + namelen > end) {
> +			inode_ref_err(fs_info, leaf, slot,
> +		"inode ref overflow, ptr %lu end %lu namelen %u",
> +				ptr, end, namelen);
> +			return -EUCLEAN;
> +		}
> +
> +		/*
> +		 * NOTE: In theory we should record all found index number
> +		 * to find any duplicated index. But that will be too time
> +		 * consuming for inodes with too many hard links.
> +		 */
> +		ptr += sizeof(*iref) + namelen;
> +	}
> +	return 0;
> +}
> +
>  /*
>   * Common point to switch the item-specific validation.
>   */
> @@ -864,6 +914,9 @@ static int check_leaf_item(struct extent_buffer *leaf,
>  	case BTRFS_XATTR_ITEM_KEY:
>  		ret = check_dir_item(leaf, key, prev_key, slot);
>  		break;
> +	case BTRFS_INODE_REF_KEY:
> +		ret = check_inode_ref(leaf, key, prev_key, slot);
> +		break;
>  	case BTRFS_BLOCK_GROUP_ITEM_KEY:
>  		ret = check_block_group_item(leaf, key, slot);
>  		break;
> 

  reply	other threads:[~2019-08-26 11:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  7:40 [PATCH 0/2] btrfs: tree-checker: Add checks to detect missing INODE_ITEM Qu Wenruo
2019-08-26  7:40 ` [PATCH 1/2] btrfs: tree-checker: Try " Qu Wenruo
2019-08-26 11:46   ` Nikolay Borisov
2019-08-26  7:40 ` [PATCH 2/2] btrfs: tree-checker: Add check for INODE_REF Qu Wenruo
2019-08-26 11:45   ` Nikolay Borisov [this message]
2019-08-26 11:50     ` Qu Wenruo
2019-09-23 15:45       ` David Sterba
2019-09-23 15:47   ` David Sterba

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=4c9195c9-5fc1-8524-e7d8-78ad1e942df7@suse.com \
    --to=nborisov@suse.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;
as well as URLs for NNTP newsgroup(s).