From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/6 v2] xfs: validate btree records on retreival
Date: Wed, 6 Jun 2018 09:00:07 +1000 [thread overview]
Message-ID: <20180605230007.GK10363@dastard> (raw)
In-Reply-To: <20180605104207.3qlaudozsmjrize7@odin.usersys.redhat.com>
On Tue, Jun 05, 2018 at 12:42:07PM +0200, Carlos Maiolino wrote:
> > + if (irec->rc_blockcount == 0 || irec->rc_blockcount > MAXREFCEXTLEN)
> > + goto out_bad_rec;
> > +
> > + /* handle special COW-staging state */
> > + realstart = irec->rc_startblock;
> > + if (realstart & XFS_REFC_COW_START) {
> > + if (irec->rc_refcount != 1)
> > + goto out_bad_rec;
> > + realstart &= ~XFS_REFC_COW_START;
> > }
> > - return error;
> > +
> > + /* check for valid extent range, including overflow */
> > + if (!xfs_verify_agbno(mp, agno, realstart))
> > + goto out_bad_rec;
> > + if (realstart > realstart + irec->rc_blockcount)
>
> I am not sure if I'm right, but I thought this ought to be ">="?
We've already caught zero length and block count greater than
2^32-1, so if the above is true we've wrapped through zero during
the addition. But we can never add 0 or 2^32 to realstart here, so
the "==" condition will not occur and we don't need to check for
it....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-06-05 23:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 6:24 [PATCH 0/6 V2] xfs: more verifications! Dave Chinner
2018-06-05 6:24 ` [PATCH 1/6] xfs: catch bad stripe alignment configurations Dave Chinner
2018-06-05 9:27 ` Carlos Maiolino
2018-06-05 6:24 ` [PATCH 2/6] xfs: verify extent size hint is valid in inode verifier Dave Chinner
2018-06-05 9:53 ` Carlos Maiolino
2018-06-05 22:56 ` Dave Chinner
2018-06-05 17:10 ` Darrick J. Wong
2018-06-07 16:16 ` Darrick J. Wong
2018-06-08 1:10 ` Dave Chinner
2018-06-08 1:23 ` Darrick J. Wong
2018-06-08 2:23 ` Eric Sandeen
2018-07-24 6:39 ` Eric Sandeen
2018-07-24 16:43 ` Darrick J. Wong
2018-08-20 15:06 ` Brian Foster
2018-08-20 15:27 ` Eric Sandeen
2018-08-20 15:36 ` Darrick J. Wong
2018-08-20 15:59 ` Brian Foster
2018-08-20 22:15 ` Dave Chinner
2018-08-21 10:56 ` Brian Foster
2018-08-22 0:41 ` Dave Chinner
2018-06-05 6:24 ` [PATCH 3/6] xfs: verify COW " Dave Chinner
2018-06-05 10:00 ` Carlos Maiolino
2018-06-05 17:09 ` Darrick J. Wong
2018-06-05 6:24 ` [PATCH 4/6] xfs: validate btree records on retreival Dave Chinner
2018-06-05 6:40 ` [PATCH 4/6 v2] " Dave Chinner
2018-06-05 10:42 ` Carlos Maiolino
2018-06-05 23:00 ` Dave Chinner [this message]
2018-06-05 17:47 ` Darrick J. Wong
2018-06-05 23:02 ` Dave Chinner
2018-06-06 1:21 ` [PATCH 4/6 v3] " Dave Chinner
2018-06-05 6:24 ` [PATCH 5/6] xfs: verify root inode more thoroughly Dave Chinner
2018-06-05 10:50 ` Carlos Maiolino
2018-06-05 17:10 ` Darrick J. Wong
2018-06-05 6:24 ` [PATCH 6/6] xfs: push corruption -> ESTALE conversion to xfs_nfs_get_inode() Dave Chinner
2018-06-05 11:12 ` Carlos Maiolino
2018-06-05 17:11 ` Darrick J. Wong
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=20180605230007.GK10363@dastard \
--to=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.