This is a note to let you know that I've just added the patch titled

    ext4: use s_csum_seed instead of i_csum_seed for xattr block

to the 3.5-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     ext4-use-s_csum_seed-instead-of-i_csum_seed-for-xattr-block.patch
and it can be found in the queue-3.5 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 41eb70dde42b2360074a559a6f1fc49860a50179 Mon Sep 17 00:00:00 2001
From: Tao Ma <[email protected]>
Date: Mon, 9 Jul 2012 16:29:27 -0400
Subject: ext4: use s_csum_seed instead of i_csum_seed for xattr block

From: Tao Ma <[email protected]>

commit 41eb70dde42b2360074a559a6f1fc49860a50179 upstream.

In xattr block operation, we use h_refcount to indicate whether the
xattr block is shared among many inodes. And xattr block csum uses
s_csum_seed if it is shared and i_csum_seed if it belongs to
one inode. But this has a problem. So consider the block is shared
first bewteen inode A and B, and B has some xattr update and CoW
the xattr block. When it updates the *old* xattr block(because
of the h_refcount change) and calls ext4_xattr_release_block, we
has no idea that inode A is the real owner of the *old* xattr
block and we can't use the i_csum_seed of inode A either in xattr
block csum calculation. And I don't think we have an easy way to
find inode A.

So this patch just removes the tricky i_csum_seed and we now uses
s_csum_seed every time for the xattr block csum. The corresponding
patch for the e2fsprogs will be sent in another patch.

This is spotted by xfstests 117.

Signed-off-by: Tao Ma <[email protected]>
Signed-off-by: "Theodore Ts'o" <[email protected]>
Acked-by: Darrick J. Wong <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/ext4/xattr.c |   11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

--- a/fs/ext4/xattr.c
+++ b/fs/ext4/xattr.c
@@ -127,19 +127,16 @@ static __le32 ext4_xattr_block_csum(stru
                                    struct ext4_xattr_header *hdr)
 {
        struct ext4_sb_info *sbi = EXT4_SB(inode->i_sb);
-       struct ext4_inode_info *ei = EXT4_I(inode);
        __u32 csum, old;
 
        old = hdr->h_checksum;
        hdr->h_checksum = 0;
-       if (le32_to_cpu(hdr->h_refcount) != 1) {
-               block_nr = cpu_to_le64(block_nr);
-               csum = ext4_chksum(sbi, sbi->s_csum_seed, (__u8 *)&block_nr,
-                                  sizeof(block_nr));
-       } else
-               csum = ei->i_csum_seed;
+       block_nr = cpu_to_le64(block_nr);
+       csum = ext4_chksum(sbi, sbi->s_csum_seed, (__u8 *)&block_nr,
+                          sizeof(block_nr));
        csum = ext4_chksum(sbi, csum, (__u8 *)hdr,
                           EXT4_BLOCK_SIZE(inode->i_sb));
+
        hdr->h_checksum = old;
        return cpu_to_le32(csum);
 }


Patches currently in stable-queue which might be from [email protected] are

queue-3.5/ext4-use-proper-csum-calculation-in-ext4_rename.patch
queue-3.5/ext4-use-s_csum_seed-instead-of-i_csum_seed-for-xattr-block.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to