From: Chao Yu <yuchao0@huawei.com>
To: <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <chao@kernel.org>,
Chao Yu <yuchao0@huawei.com>
Subject: [PATCH] f2fs: add sanity check for quota sysfile ino
Date: Mon, 29 Jan 2018 16:29:33 +0800 [thread overview]
Message-ID: <20180129082933.64556-1-yuchao0@huawei.com> (raw)
Add missing sanity check for quota sysfile ino.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
---
fs/f2fs/super.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 368f63d7bad2..6011071688ca 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -2116,6 +2116,25 @@ static int sanity_check_raw_super(struct f2fs_sb_info *sbi,
return 1;
}
+ /* check quota sysfile ino info */
+ if (raw_super->feature & cpu_to_le32(F2FS_FEATURE_QUOTA_INO)) {
+ if (le32_to_cpu(raw_super->qf_ino[0]) != 4 ||
+ le32_to_cpu(raw_super->qf_ino[1]) != 5) {
+ f2fs_msg(sb, KERN_INFO,
+ "Invalid Quota Ino: user_ino(%u), grp_ino(%u)",
+ le32_to_cpu(raw_super->qf_ino[0]),
+ le32_to_cpu(raw_super->qf_ino[1]));
+ return 1;
+ }
+ if (raw_super->feature & cpu_to_le32(F2FS_FEATURE_PRJQUOTA) &&
+ le32_to_cpu(raw_super->qf_ino[2]) != 6) {
+ f2fs_msg(sb, KERN_INFO,
+ "Invalid Quota Ino: prj_ino(%u)",
+ le32_to_cpu(raw_super->qf_ino[2]));
+ return 1;
+ }
+ }
+
if (le32_to_cpu(raw_super->segment_count) > F2FS_MAX_SEGMENT) {
f2fs_msg(sb, KERN_INFO,
"Invalid segment count (%u)",
--
2.15.0.55.gc2ece9dc4de6
next reply other threads:[~2018-01-29 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 8:29 Chao Yu [this message]
2018-01-31 1:35 ` [PATCH] f2fs: add sanity check for quota sysfile ino Jaegeuk Kim
2018-01-31 2:01 ` Chao Yu
2018-01-31 2:36 ` Jaegeuk Kim
2018-01-31 3:38 ` Chao Yu
2018-01-31 3:49 ` Jaegeuk Kim
2018-01-31 6:02 ` Chao Yu
2018-01-31 21:57 ` Jaegeuk Kim
2018-02-01 13:41 ` Chao Yu
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=20180129082933.64556-1-yuchao0@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).