public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: fix btree scrub checking with regards to root-in-inode
Date: Tue, 19 Mar 2019 09:00:52 -0400	[thread overview]
Message-ID: <20190319130051.GB23863@bfoster> (raw)
In-Reply-To: <20190318164336.GO4929@magnolia>

On Mon, Mar 18, 2019 at 09:43:36AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> In xchk_btree_check_owner, we can be passed a null buffer pointer.  This
> should only happen for the root of a root-in-inode btree type, but we
> should program defensively in case the btree cursor state ever gets
> screwed up and we get a null buffer anyway.
> 
> Coverity-id: 1438713
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---

Reviewed-by: Brian Foster <bfoster@redhat.com>

>  fs/xfs/scrub/btree.c |   11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/scrub/btree.c b/fs/xfs/scrub/btree.c
> index 6271a277eabe..cf4046c9e250 100644
> --- a/fs/xfs/scrub/btree.c
> +++ b/fs/xfs/scrub/btree.c
> @@ -481,8 +481,17 @@ xchk_btree_check_owner(
>  	struct xfs_btree_cur	*cur = bs->cur;
>  	struct check_owner	*co;
>  
> -	if ((cur->bc_flags & XFS_BTREE_ROOT_IN_INODE) && bp == NULL)
> +	/*
> +	 * In theory, xfs_btree_get_block should only give us a null buffer
> +	 * pointer for the root of a root-in-inode btree type, but we need
> +	 * to check defensively here in case the cursor state is also screwed
> +	 * up.
> +	 */
> +	if (bp == NULL) {
> +		if (!(cur->bc_flags & XFS_BTREE_ROOT_IN_INODE))
> +			xchk_btree_set_corrupt(bs->sc, bs->cur, level);
>  		return 0;
> +	}
>  
>  	/*
>  	 * We want to cross-reference each btree block with the bnobt

      reply	other threads:[~2019-03-19 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 16:43 [PATCH] xfs: fix btree scrub checking with regards to root-in-inode Darrick J. Wong
2019-03-19 13:00 ` Brian Foster [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=20190319130051.GB23863@bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@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