From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 3/5] xfs: directory scrubber must walk through data block to offset
Date: Mon, 15 Jan 2018 11:53:30 -0800 [thread overview]
Message-ID: <20180115195330.GA5602@magnolia> (raw)
In-Reply-To: <20180115144143.GC47688@bfoster.bfoster>
On Mon, Jan 15, 2018 at 09:41:44AM -0500, Brian Foster wrote:
> On Fri, Jan 12, 2018 at 02:04:18PM -0800, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > In xfs_scrub_dir_rec, we must walk through the directory block entries
> > to arrive at the offset given by the hash structure. If we blindly
> > trust the hash address, we can end up midway into a directory entry and
> > stray outside the block. Found by lastbit fuzzing lents[3].address in
> > xfs/390 with KASAN enabled.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > ---
> > fs/xfs/libxfs/xfs_dir2.h | 1 +
> > fs/xfs/libxfs/xfs_dir2_data.c | 19 +++++++++++++++++++
> > fs/xfs/scrub/dir.c | 26 +++++++++++++++++++++++++-
> > 3 files changed, 45 insertions(+), 1 deletion(-)
> >
> >
> > diff --git a/fs/xfs/libxfs/xfs_dir2.h b/fs/xfs/libxfs/xfs_dir2.h
> > index 1a8f2cf..2c77195 100644
> > --- a/fs/xfs/libxfs/xfs_dir2.h
> > +++ b/fs/xfs/libxfs/xfs_dir2.h
> > @@ -340,5 +340,6 @@ xfs_dir2_leaf_tail_p(struct xfs_da_geometry *geo, struct xfs_dir2_leaf *lp)
> > #define XFS_READDIR_BUFSIZE (32768)
> >
> > unsigned char xfs_dir3_get_dtype(struct xfs_mount *mp, uint8_t filetype);
> > +void *xfs_dir3_data_endp(struct xfs_mount *mp, struct xfs_dir2_data_hdr *hdr);
> >
> > #endif /* __XFS_DIR2_H__ */
> ...
> > diff --git a/fs/xfs/scrub/dir.c b/fs/xfs/scrub/dir.c
> > index f5a0d17..6acbed0 100644
> > --- a/fs/xfs/scrub/dir.c
> > +++ b/fs/xfs/scrub/dir.c
> > @@ -200,6 +200,7 @@ xfs_scrub_dir_rec(
> > struct xfs_inode *dp = ds->dargs.dp;
> > struct xfs_dir2_data_entry *dent;
> > struct xfs_buf *bp;
> > + char *p, *endp;
> > xfs_ino_t ino;
> > xfs_dablk_t rec_bno;
> > xfs_dir2_db_t db;
> > @@ -239,8 +240,31 @@ xfs_scrub_dir_rec(
> > }
> > xfs_scrub_buffer_recheck(ds->sc, bp);
> >
> > - /* Retrieve the entry, sanity check it, and compare hashes. */
> > dent = (struct xfs_dir2_data_entry *)(((char *)bp->b_addr) + off);
> > +
> > + /* Make sure we got a real directory entry. */
> > + p = (char *)mp->m_dir_inode_ops->data_entry_p(bp->b_addr);
> > + endp = xfs_dir3_data_endp(mp, bp->b_addr);
>
> If this helper can return NULL perhaps we should check for that case
> too? Otherwise looks fine:
Yep, good catch; fixed.
--D
> Reviewed-by: Brian Foster <bfoster@redhat.com>
>
> > + while (p < endp) {
> > + struct xfs_dir2_data_entry *dep;
> > + struct xfs_dir2_data_unused *dup;
> > +
> > + dup = (struct xfs_dir2_data_unused *)p;
> > + if (be16_to_cpu(dup->freetag) == XFS_DIR2_DATA_FREE_TAG) {
> > + p += be16_to_cpu(dup->length);
> > + continue;
> > + }
> > + dep = (struct xfs_dir2_data_entry *)p;
> > + if (dep == dent)
> > + break;
> > + p += mp->m_dir_inode_ops->data_entsize(dep->namelen);
> > + }
> > + if (p == endp) {
> > + xfs_scrub_fblock_set_corrupt(ds->sc, XFS_DATA_FORK, rec_bno);
> > + goto out_relse;
> > + }
> > +
> > + /* Retrieve the entry, sanity check it, and compare hashes. */
> > ino = be64_to_cpu(dent->inumber);
> > hash = be32_to_cpu(ent->hashval);
> > tag = be16_to_cpup(dp->d_ops->data_entry_tag_p(dent));
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-15 19:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 22:03 [PATCH 0/5] xfs: kasan/ubsan fixes Darrick J. Wong
2018-01-12 22:04 ` [PATCH 1/5] xfs: check sb_agblocks and sb_agblklog when validating superblock Darrick J. Wong
2018-01-15 14:41 ` Brian Foster
2018-01-15 19:49 ` Darrick J. Wong
2018-01-15 20:03 ` [PATCH v2 " Darrick J. Wong
2018-01-15 21:31 ` Dave Chinner
2018-01-16 7:00 ` Darrick J. Wong
2018-01-16 12:48 ` Brian Foster
2018-01-16 17:34 ` Darrick J. Wong
2018-01-16 18:02 ` Brian Foster
2018-01-16 21:10 ` Darrick J. Wong
2018-01-17 1:20 ` [PATCH v3 " Darrick J. Wong
2018-01-17 12:55 ` Brian Foster
2018-01-12 22:04 ` [PATCH 2/5] xfs: don't iunlock unlocked inodes Darrick J. Wong
2018-01-15 14:41 ` Brian Foster
2018-01-12 22:04 ` [PATCH 3/5] xfs: directory scrubber must walk through data block to offset Darrick J. Wong
2018-01-15 14:41 ` Brian Foster
2018-01-15 19:53 ` Darrick J. Wong [this message]
2018-01-15 20:04 ` [PATCH v2 " Darrick J. Wong
2018-01-15 21:56 ` Dave Chinner
2018-01-16 7:01 ` Darrick J. Wong
2018-01-16 23:30 ` [PATCH v3 " Darrick J. Wong
2018-01-17 0:29 ` Dave Chinner
2018-01-12 22:04 ` [PATCH 4/5] xfs: attr leaf verifier needs to check for obviously bad count Darrick J. Wong
2018-01-15 14:42 ` Brian Foster
2018-01-15 19:59 ` Darrick J. Wong
2018-01-15 20:05 ` [PATCH v2 " Darrick J. Wong
2018-01-16 12:50 ` Brian Foster
2018-01-16 23:32 ` Darrick J. Wong
2018-01-12 22:04 ` [PATCH 5/5] xfs: btree format ifork loader should check for zero numrecs Darrick J. Wong
2018-01-15 14:42 ` Brian Foster
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=20180115195330.GA5602@magnolia \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.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