From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Jia-Ju Bai <baijiaju1990@gmail.com>
Cc: bfoster@redhat.com, sandeen@sandeen.net,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs: xfs: Fix possible null-pointer dereferences in xchk_da_btree_block_check_sibling()
Date: Tue, 30 Jul 2019 07:41:22 -0700 [thread overview]
Message-ID: <20190730144122.GP1561054@magnolia> (raw)
In-Reply-To: <20190730023206.14587-1-baijiaju1990@gmail.com>
On Tue, Jul 30, 2019 at 10:32:06AM +0800, Jia-Ju Bai wrote:
> In xchk_da_btree_block_check_sibling(), there is an if statement on
> line 274 to check whether ds->state->altpath.blk[level].bp is NULL:
> if (ds->state->altpath.blk[level].bp)
>
> When ds->state->altpath.blk[level].bp is NULL, it is used on line 281:
> xfs_trans_brelse(..., ds->state->altpath.blk[level].bp);
> struct xfs_buf_log_item *bip = bp->b_log_item;
> ASSERT(bp->b_transp == tp);
>
> Thus, possible null-pointer dereferences may occur.
>
> To fix these bugs, ds->state->altpath.blk[level].bp is checked before
> being used.
>
> These bugs are found by a static analysis tool STCheck written by us.
>
> Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> v2:
> * Adjust the code and add an assignment.
> Thank Darrick J. Wong for helpful advice.
>
> ---
> fs/xfs/scrub/dabtree.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/fs/xfs/scrub/dabtree.c b/fs/xfs/scrub/dabtree.c
> index 94c4f1de1922..77ff9f97bcda 100644
> --- a/fs/xfs/scrub/dabtree.c
> +++ b/fs/xfs/scrub/dabtree.c
> @@ -278,7 +278,11 @@ xchk_da_btree_block_check_sibling(
> /* Compare upper level pointer to sibling pointer. */
> if (ds->state->altpath.blk[level].blkno != sibling)
> xchk_da_set_corrupt(ds, level);
> - xfs_trans_brelse(ds->dargs.trans, ds->state->altpath.blk[level].bp);
> + if (ds->state->altpath.blk[level].bp) {
> + xfs_trans_brelse(ds->dargs.trans,
> + ds->state->altpath.blk[level].bp);
> + ds->state->altpath.blk[level].bp = NULL;
> + }
> out:
> return error;
> }
> --
> 2.17.0
>
prev parent reply other threads:[~2019-07-30 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 2:32 [PATCH v2] fs: xfs: Fix possible null-pointer dereferences in xchk_da_btree_block_check_sibling() Jia-Ju Bai
2019-07-30 14:41 ` Darrick J. Wong [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=20190730144122.GP1561054@magnolia \
--to=darrick.wong@oracle.com \
--cc=baijiaju1990@gmail.com \
--cc=bfoster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).