From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>, linux-xfs <linux-xfs@vger.kernel.org>
Cc: "Xu, Wen" <wen.xu@gatech.edu>
Subject: [PATCH 2/2 V3] xfs: verify size-vs-format for symlinks & dirs
Date: Mon, 24 Sep 2018 22:00:39 -0500 [thread overview]
Message-ID: <1e55b111-eae4-b0cf-0221-c96eb3f17b77@redhat.com> (raw)
In-Reply-To: <ba65356c-2b57-75fb-0436-804913285809@redhat.com>
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>
Reviewed-by: Brian Foster <bfoster@redhat.com>
---
V2: restructure code & tests per Dave's suggestion on the V1 patch.
V3: rewrite dave's comments per brian's suggestions
diff --git a/fs/xfs/libxfs/xfs_inode_fork.c b/fs/xfs/libxfs/xfs_inode_fork.c
index f9acf1d436f6..d1a58e7a872f 100644
--- a/fs/xfs/libxfs/xfs_inode_fork.c
+++ b/fs/xfs/libxfs/xfs_inode_fork.c
@@ -704,12 +704,33 @@ 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;
+
+ /*
+ * 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.
+ */
+ if (ip->i_d.di_format != XFS_DINODE_FMT_LOCAL) {
+ switch (mode & S_IFMT) {
+ case S_IFDIR:
+ if (ip->i_d.di_size < mp->m_dir_geo->blksize)
+ return __this_address;
+ 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:
next prev parent reply other threads:[~2018-09-25 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 2:56 [PATCH 0/2 V3] xfs: validate size vs format Eric Sandeen
2018-09-25 2:58 ` [PATCH 1/2 V3] xfs: validate inode di_forkoff Eric Sandeen
2018-09-25 3:00 ` Eric Sandeen [this message]
2018-09-30 3:25 ` [PATCH 2/2 V3] xfs: verify size-vs-format for symlinks & dirs Dave Chinner
2018-09-30 5:06 ` Eric Sandeen
2018-09-30 6:05 ` Dave Chinner
2018-09-30 17:54 ` Eric Sandeen
2018-09-26 0:13 ` [PATCH 0/2 V3] xfs: validate size vs format 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=1e55b111-eae4-b0cf-0221-c96eb3f17b77@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=wen.xu@gatech.edu \
/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).