From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/2 V2] xfs: verify size-vs-format for symlinks & dirs
Date: Mon, 24 Sep 2018 13:06:58 -0400 [thread overview]
Message-ID: <20180924170658.GB60179@bfoster> (raw)
In-Reply-To: <d2648726-e4f9-a5a7-c9b1-560ad03d3e67@redhat.com>
On Mon, Sep 10, 2018 at 05:24:17PM -0500, Eric Sandeen wrote:
> Today, xfs_ifork_verify_data() will simply skip verification if the inode
> claims to be in non-local format. However, nothing catches the case where
> the size for the format is too small to be non-local. xfs_repair tests
> for this mismatch in process_check_inode_sizes(), so do the same in this
> verifier.
>
> Reported-by: Xu, Wen <wen.xu@gatech.edu>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=200925
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> V2: restructure code & tests per Dave's suggestion on the V1 patch.
>
> diff --git a/fs/xfs/libxfs/xfs_inode_fork.c b/fs/xfs/libxfs/xfs_inode_fork.c
> index 183ec0cb8921..d6a137f5e207 100644
> --- a/fs/xfs/libxfs/xfs_inode_fork.c
> +++ b/fs/xfs/libxfs/xfs_inode_fork.c
> @@ -732,12 +732,32 @@ xfs_ifork_verify_data(
> struct xfs_inode *ip,
> struct xfs_ifork_ops *ops)
> {
> - /* Non-local data fork, we're done. */
> - if (ip->i_d.di_format != XFS_DINODE_FMT_LOCAL)
> + struct xfs_mount *mp = ip->i_mount;
> + int mode = VFS_I(ip)->i_mode;
> +
> + if (ip->i_d.di_format != XFS_DINODE_FMT_LOCAL) {
> + /*
> + * types that can be in local form need size checks
> + * to ensure they have the right amount of data in
> + * them to be in non-local form
> + */
Just another nit... I had to read the comment a few times to understand
how it relates to the code. Could we perhaps move it above the if check
and reword it to something like:
/*
* If this is a non-local format directory or symlink, verify the inode
* size is consistent with non-local format.
*/
> + switch (mode & S_IFMT) {
> + case S_IFDIR:
> + if (ip->i_d.di_size < mp->m_dir_geo->blksize)
> + return __this_address;
Hmm, where does the ->blksize check come from? The dir shortform
transition code looks like it keys off of XFS_IFORK_DSIZE()..
Ah Ok, I went back and read Dave's feedback on the v1 post. If we want
to use this to also cover a range of invalid dir sizes, could we
incorporate that into the above comment as well so it's more clear?
E.g., change the above to something like:
/*
* Verify non-local format forks have a valid size. Symlinks must have
* outgrown the data fork size. The same goes for non-local dirs, but
* dirs grow at dirblock granularity. Perform a slightly stronger check
* and require the dir is at least one dirblock in size.
*/
Otherwise with the comment fixups:
Reviewed-by: Brian Foster <bfoster@redhat.com>
> + break;
> + case S_IFLNK:
> + if (ip->i_d.di_size <= XFS_IFORK_DSIZE(ip))
> + return __this_address;
> + break;
> + default:
> + break;
> + }
> return NULL;
> + }
>
> /* Check the inline data fork if there is one. */
> - switch (VFS_I(ip)->i_mode & S_IFMT) {
> + switch (mode & S_IFMT) {
> case S_IFDIR:
> return ops->verify_dir(ip);
> case S_IFLNK:
>
prev parent reply other threads:[~2018-09-24 23:10 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
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 [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=20180924170658.GB60179@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).