From: Sheng Yong <shengyong1@huawei.com>
To: jaegeuk@kernel.org, yuchao0@huawei.com
Cc: hyojun@google.com, miaoxie@huawei.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: [RFC PATCH v2 4/7] fsck.f2fs: integrate sanity_check_inode to __check_inode_mode
Date: Fri, 23 Feb 2018 11:17:58 +0800 [thread overview]
Message-ID: <20180223031801.231805-5-shengyong1@huawei.com> (raw)
In-Reply-To: <20180223031801.231805-1-shengyong1@huawei.com>
In sanity_check_nid, __check_inode_mode will check i_mode value of an
inode. So integrate sanity_check_inode to __check_inode_mode to clean
up the code.
Signed-off-by: Sheng Yong <shengyong1@huawei.com>
---
fsck/fsck.c | 33 +++++++++++----------------------
1 file changed, 11 insertions(+), 22 deletions(-)
diff --git a/fsck/fsck.c b/fsck/fsck.c
index 0a37f7a..f6391e9 100644
--- a/fsck/fsck.c
+++ b/fsck/fsck.c
@@ -334,6 +334,15 @@ static int __check_inode_mode(u32 nid, enum FILE_TYPE ftype, u32 mode)
{
if (ftype >= F2FS_FT_MAX)
return 0;
+ /* f2fs_iget will return -EIO if mode is not valid file type */
+ if (!S_ISLNK(mode) && !S_ISREG(mode) && !S_ISDIR(mode) &&
+ !S_ISCHR(mode) && !S_ISBLK(mode) && !S_ISFIFO(mode) &&
+ !S_ISSOCK(mode)) {
+ ASSERT_MSG("inode [0x%x] unknown file type i_mode [0x%x]",
+ nid, mode);
+ return -1;
+ }
+
if (S_ISLNK(mode) && ftype != F2FS_FT_SYMLINK)
goto err;
if (S_ISREG(mode) && ftype != F2FS_FT_REG_FILE)
@@ -350,7 +359,8 @@ static int __check_inode_mode(u32 nid, enum FILE_TYPE ftype, u32 mode)
goto err;
return 0;
err:
- ASSERT_MSG("mismatch i_mode [0x%x] [0x%x vs. 0x%x]", nid, ftype, mode);
+ ASSERT_MSG("inode [0x%x] mismatch i_mode [0x%x vs. 0x%x]",
+ nid, ftype, mode);
return -1;
}
@@ -465,25 +475,6 @@ static int sanity_check_nid(struct f2fs_sb_info *sbi, u32 nid,
return 0;
}
-static int sanity_check_inode(struct f2fs_sb_info *sbi, struct f2fs_node *node)
-{
- struct f2fs_fsck *fsck = F2FS_FSCK(sbi);
- struct f2fs_inode *fi = &node->i;
-
- if (!(le16_to_cpu(fi->i_mode) & S_IFMT)) {
- ASSERT_MSG("i_mode is not valid. [0x%x]", le16_to_cpu(fi->i_mode));
- goto remove_node;
- }
-
- return 0;
-
-remove_node:
- f2fs_set_bit(le32_to_cpu(node->footer.ino), fsck->nat_area_bitmap);
- fsck->chk.valid_blk_cnt--;
- fsck->chk.valid_node_cnt--;
- return -EINVAL;
-}
-
static int fsck_chk_xattr_blk(struct f2fs_sb_info *sbi, u32 ino,
u32 x_nid, u32 *blk_cnt)
{
@@ -528,8 +519,6 @@ int fsck_chk_node_blk(struct f2fs_sb_info *sbi, struct f2fs_inode *inode,
if (ntype == TYPE_INODE) {
struct f2fs_fsck *fsck = F2FS_FSCK(sbi);
- if (sanity_check_inode(sbi, node_blk))
- goto err;
fsck_chk_inode_blk(sbi, nid, ftype, node_blk, blk_cnt, &ni, child);
quota_add_inode_usage(fsck->qctx, nid, &node_blk->i);
} else {
--
2.14.1
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-02-23 3:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 3:17 [RFC PATCH v2 0/7] f2fs-tools: introduce F2FS_FEATURE_LOST_FOUND feature Sheng Yong
2018-02-23 3:17 ` [RFC PATCH v2 1/7] fsck.f2fs: fix typo Sheng Yong
2018-02-23 3:17 ` [RFC PATCH v2 2/7] mkfs.f2fs: introduce mkfs parameters in f2fs_configuration Sheng Yong
2018-02-23 3:17 ` [RFC PATCH v2 3/7] f2fs-tools: init f2fs_configuration as 0 Sheng Yong
2018-02-23 3:17 ` Sheng Yong [this message]
2018-02-23 3:17 ` [RFC PATCH v2 5/7] mkfs.f2fs: create lost+found directory Sheng Yong
2018-02-28 5:25 ` Jaegeuk Kim
2018-02-23 3:18 ` [RFC PATCH v2 6/7] fsck.f2fs: read nat block if nat entry is invalid Sheng Yong
2018-02-23 3:18 ` [RFC PATCH v2 7/7] fsck.f2fs: reconnect unreachable files to lost+found Sheng Yong
[not found] ` <0c849139-fdbe-9362-770c-ad4e9da57142@huawei.com>
[not found] ` <8abbaedf-ae3b-741f-d36f-d65f96739065@huawei.com>
2018-02-28 5:16 ` Jaegeuk Kim
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=20180223031801.231805-5-shengyong1@huawei.com \
--to=shengyong1@huawei.com \
--cc=hyojun@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=miaoxie@huawei.com \
--cc=yuchao0@huawei.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).