[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1375436989-18948-6-git-send-email-wenqing.lz@taobao.com>
Date: Fri, 2 Aug 2013 17:49:32 +0800
From: Zheng Liu <gnehzuil.liu@...il.com>
To: linux-ext4@...r.kernel.org
Cc: Theodore Ts'o <tytso@....edu>, Zheng Liu <wenqing.lz@...bao.com>
Subject: [PATCH v1 05/22] libext2fs: handle inline_data in block iterator function
From: Zheng Liu <wenqing.lz@...bao.com>
We needn't traverse blocks for an inode which has inline data because no
block belongs to it. After applied this patch, the following commands
in debugfs can handle inline_data feature:
- icheck
- blocks
- filefrag
In some places, block iterator functions are used to traverse blocks of
directory. In this case, we need to check whether inode has inline_data
flag or not, and handle it manually.
Signed-off-by: Theodore Ts'o <tytso@....edu>
Signed-off-by: Zheng Liu <wenqing.lz@...bao.com>
---
lib/ext2fs/block.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/lib/ext2fs/block.c b/lib/ext2fs/block.c
index b8c6879..b194ca8 100644
--- a/lib/ext2fs/block.c
+++ b/lib/ext2fs/block.c
@@ -345,6 +345,13 @@ errcode_t ext2fs_block_iterate3(ext2_filsys fs,
return ctx.errcode;
/*
+ * If an inode has inline data, we needn't traverse its blocks
+ * because no block belong to this inode.
+ */
+ if (inode.i_flags & EXT4_INLINE_DATA_FL)
+ return ctx.errcode;
+
+ /*
* Check to see if we need to limit large files
*/
if (flags & BLOCK_FLAG_NO_LARGE) {
--
1.7.9.7
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists