From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] xfs: validate inode di_forkoff
Date: Mon, 24 Sep 2018 13:04:48 -0400 [thread overview]
Message-ID: <20180924170447.GA60179@bfoster> (raw)
In-Reply-To: <da670f4a-6ae7-fbe7-94db-b6a4e6bb0c9e@redhat.com>
On Mon, Sep 10, 2018 at 05:22:08PM -0500, Eric Sandeen wrote:
> Verify the inode di_forkoff, lifted from xfs_repair's
> process_check_inode_forkoff().
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> diff --git a/fs/xfs/libxfs/xfs_inode_buf.c b/fs/xfs/libxfs/xfs_inode_buf.c
> index 30d1d60f1d46..8d76637a49a7 100644
> --- a/fs/xfs/libxfs/xfs_inode_buf.c
> +++ b/fs/xfs/libxfs/xfs_inode_buf.c
> @@ -415,6 +415,31 @@ xfs_dinode_verify_fork(
> return NULL;
> }
>
> +static xfs_failaddr_t
> +xfs_dinode_verify_forkoff(
> + struct xfs_dinode *dip,
> + struct xfs_mount *mp)
> +{
> + if (dip->di_forkoff == 0)
> + return NULL;
I think it would be good to use XFS_DFORK_Q() here, just to be
consistent with the other, similar checks. Otherwise looks good:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> +
> + switch (dip->di_format) {
> + case XFS_DINODE_FMT_DEV:
> + if (dip->di_forkoff != (roundup(sizeof(xfs_dev_t), 8) >> 3))
> + return __this_address;
> + break;
> + case XFS_DINODE_FMT_LOCAL: /* fall through ... */
> + case XFS_DINODE_FMT_EXTENTS: /* fall through ... */
> + case XFS_DINODE_FMT_BTREE:
> + if (dip->di_forkoff >= (XFS_LITINO(mp, dip->di_version) >> 3))
> + return __this_address;
> + break;
> + default:
> + return __this_address;
> + }
> + return NULL;
> +}
> +
> xfs_failaddr_t
> xfs_dinode_verify(
> struct xfs_mount *mp,
> @@ -470,6 +498,11 @@ xfs_dinode_verify(
> if (mode && (flags & XFS_DIFLAG_REALTIME) && !mp->m_rtdev_targp)
> return __this_address;
>
> + /* check for illegal values of di_forkoff */
> + fa = xfs_dinode_verify_forkoff(dip, mp);
> + if (fa)
> + return fa;
> +
> /* Do we have appropriate data fork formats for the mode? */
> switch (mode & S_IFMT) {
> case S_IFIFO:
>
next prev parent reply other threads:[~2018-09-24 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 22:18 [PATCH 0/2] xfs: validate size vs format, take 2 Eric Sandeen
2018-09-10 22:22 ` [PATCH 1/2] xfs: validate inode di_forkoff Eric Sandeen
2018-09-24 17:04 ` Brian Foster [this message]
2018-09-25 2:50 ` Eric Sandeen
2018-09-10 22:24 ` [PATCH 2/2 V2] xfs: verify size-vs-format for symlinks & dirs Eric Sandeen
2018-09-24 17:06 ` 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=20180924170447.GA60179@bfoster \
--to=bfoster@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).