[Ocfs2-devel] [PATCH 0/2] ocfs2: two fixes for xattr

[Tiger Yang]

Hi,

For EAs data structure in inode/block are little different from them in
bucket. These two patches try to make them same for the most part.

The first patch set xh_free_start and xh_name_value_len when EAs in
inode/block. xh_free_start is useful to keep the minimum offset of the
xattr name/value. But xh_name_value_len is not very useful because we 
don't have "hole" when EAs in inode/block, we just calculate and set it 
here, maybe it's useful for fsck.

The second patch reserve a blank space between xattr entry and 
name/value when EAs in bucket. This is same as EAs in inode/block and is 
useful in fsck.

Thanks,
tiger