Andreas Dilger wrote:
The problem was in the recently-added "extent sanity checks", and has
also been fixed:

Signed-off-by: Andreas Dilger <[EMAIL PROTECTED]>
Signed-off-by: Alex Tomas <[EMAIL PROTECTED]>
Signed-off-by: Johann Lombardi <[EMAIL PROTECTED]>

diff -u linux-2.6.18.8/fs/ext3/extents.c linux-2.6.18.8/fs/ext3/extents.c
--- linux-2.6.18.8/fs/ext3/extents.c    2007-06-20 18:54:00.000000000 +0200
+++ linux-2.6.18.8/fs/ext3/extents.c    2007-06-20 18:54:00.000000000 +0200
@@ -1069,7 +1069,7 @@ ext3_ext_search_right(struct inode *inode,
                if (bh == NULL)
                        return -EIO;
                eh = ext_block_hdr(bh);
-               if (ext3_ext_check_header(inode, eh, depth)) {
+               if (ext3_ext_check_header(inode, eh, path->p_depth - depth)) {
                        brelse(bh);
                        return -EIO;
                }

Thanks Andreas, I confirm this patch fixes the problem.
  Valérie
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to