From: Thiemo Nagel <thiemo.nagel@ph.tum.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [PATCH] ext4: add checks of block references for non-extent inodes
Date: Thu, 12 Mar 2009 18:17:10 +0100 [thread overview]
Message-ID: <49B94396.2020800@ph.tum.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
Dear Ted,
this follows your suggestion from 2009-02-05. The patch is done
analogous to Aneesh Kumar's patches for extent validation. It is based
on 2.6.29-rc7 with Aneesh's patches:
ext4: Add checks to validate extent entries
ext4: Validate extent details only when read from the disk
Kind regards,
Signed-off-by: Thiemo Nagel <thiemo.nagel@ph.tum.de>
[-- Attachment #2: add-blockrefs-checks_vs_2.6.29-rc7.patch --]
[-- Type: text/x-patch, Size: 1753 bytes --]
--- download/linux-2.6.29-rc7-vanilla-extcheck/fs/ext4/inode.c 2009-03-12 16:10:31.000000000 +0100
+++ linux-2.6.29-rc7/fs/ext4/inode.c 2009-03-12 16:09:27.000000000 +0100
@@ -371,6 +371,34 @@
return n;
}
+static int __ext4_check_blockref(const char *function, struct inode *inode,
+ unsigned int *p, unsigned int max) {
+
+ struct ext4_super_block *es = EXT4_SB(inode->i_sb)->s_es;
+ unsigned int offset = 0;
+ while (offset < max && p[offset]) {
+ if (unlikely(p[offset] < le32_to_cpu(es->s_first_data_block) ||
+ (p[offset] > ext4_blocks_count(es)))) {
+ ext4_error(inode->i_sb, function,
+ "bad block reference in inode #%lu, "
+ "offset=%u, blockref=%u",
+ inode->i_ino, offset, p[offset]);
+ return -EIO;
+ }
+ offset++;
+ }
+ return 0;
+}
+
+
+#define ext4_check_indirect_blockref(inode, bh) \
+ __ext4_check_blockref(__func__, inode, (__le32 *)(bh)->b_data, \
+ EXT4_ADDR_PER_BLOCK((inode)->i_sb))
+
+#define ext4_check_inode_blockref(inode) \
+ __ext4_check_blockref(__func__, inode, EXT4_I(inode)->i_data, \
+ EXT4_NDIR_BLOCKS)
+
/**
* ext4_get_branch - read the chain of indirect blocks leading to data
* @inode: inode in question
@@ -418,6 +446,9 @@
bh = sb_bread(sb, le32_to_cpu(p->key));
if (!bh)
goto failure;
+ if (ext4_check_indirect_blockref(inode, bh))
+ goto failure;
+
add_chain(++p, bh, (__le32 *)bh->b_data + *++offsets);
/* Reader: end */
if (!p->key)
@@ -4302,11 +4333,13 @@
if (ei->i_flags & EXT4_EXTENTS_FL) {
/* Validate extent which is part of inode */
ret = ext4_ext_check_inode(inode);
- if (ret) {
- brelse(bh);
- goto bad_inode;
- }
next reply other threads:[~2009-03-12 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 17:17 Thiemo Nagel [this message]
2009-03-12 17:20 ` [PATCH] ext4: check block references only when read from disk Thiemo Nagel
2009-03-12 17:22 ` Thiemo Nagel
2009-03-20 14:15 ` [PATCH v2] ext4: add checks of block references for non-extent inodes Thiemo Nagel
2009-03-27 21:05 ` Theodore Tso
2009-03-28 1:10 ` Theodore Tso
2009-03-30 10:43 ` Aneesh Kumar K.V
2009-03-31 8:41 ` Thiemo Nagel
2009-03-31 12:37 ` Theodore Tso
2009-03-31 12:50 ` Thiemo Nagel
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=49B94396.2020800@ph.tum.de \
--to=thiemo.nagel@ph.tum.de \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.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).