public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Filipe Manana <fdmanana@kernel.org>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: improve error reporting in lookup_inline_extent_backref
Date: Wed, 27 Apr 2022 13:14:56 +0100	[thread overview]
Message-ID: <YmkzwFQHmv1etu9z@debian9.Home> (raw)
In-Reply-To: <20220427100344.700330-1-nborisov@suse.com>

On Wed, Apr 27, 2022 at 01:03:44PM +0300, Nikolay Borisov wrote:
> When iterating the backrefs in an extent item if the ptr to the
> 'current' backref record goes beyond the extent item a warning is
> generated and -ENOENT is returned. However what's more appropriate to
> debug such cases would be to return EUCLEAN and also print identifying
> information about the performed search as well as the current content of
> the leaf containing the possibly corrupted extent item.
> 
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> ---
> V2:
>  * Removed WARN_ON and instead introduced btrfs_crit as an error printing
>  mechanism
>  * Now prints a proper error message with information about the searched reference
>  fs/btrfs/extent-tree.c | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
> index 963160a0c393..5e29c2cee46e 100644
> --- a/fs/btrfs/extent-tree.c
> +++ b/fs/btrfs/extent-tree.c
> @@ -895,7 +895,14 @@ int lookup_inline_extent_backref(struct btrfs_trans_handle *trans,
>  	err = -ENOENT;
>  	while (1) {
>  		if (ptr >= end) {
> -			WARN_ON(ptr > end);
> +			if (ptr > end) {
> +				err = -EUCLEAN;
> +				btrfs_crit(fs_info,
> +"overrun extent record at slot %lu [%llu BTRFS_EXTENT_ITEM_KEY %llu] while looking for inline extent for root %llu owner %llu offset %llu",
> +				path->slots[0], bytenr, num_bytes,
> +				root_objectid, root_objectid, owner, offset);

Printing 'parent' is also needed in order to figure out what type of reference
we were looking for.

Also, %d can be used to print the slot, as path->slots is an int array.

> +				btrfs_print_leaf(path->nodes[0]);

The leaf should be dumped before printing the message, see:

https://btrfs.wiki.kernel.org/index.php/Development_notes#Output

Other than that, it looks fine.

Thanks.

> +			}
>  			break;
>  		}
>  		iref = (struct btrfs_extent_inline_ref *)ptr;
> --
> 2.25.1
> 

      parent reply	other threads:[~2022-04-27 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 10:03 [PATCH v2] btrfs: improve error reporting in lookup_inline_extent_backref Nikolay Borisov
2022-04-27 11:57 ` [PATCH v3] " Nikolay Borisov
2022-04-27 12:14 ` Filipe Manana [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=YmkzwFQHmv1etu9z@debian9.Home \
    --to=fdmanana@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@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