ocfs2: two fixes for xattr -v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ocfs2: set xh_free_start when xattr header in inode/blockfs/ fs/ | +73 | 0 replies | |
| 1/2 | ocfs2: set xh_free_start when xattr header in inode/block | +0 | 1 reply | |
| 2/2 | ocfs2: set gap to seperate entry and value when xattr in bucketfs/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Ocfs2-devel] [PATCH 0/2] ocfs2: two fixes for xattr -v2
Hi,
I have fixed the problems in version 1 patches. These two patches based on the latest main line kernel.
Thanks,
tiger
Quoted 12 lines
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_startandxh_name_value_lenwhen EAs in inode/block.xh_free_startis useful to keep the minimum offset of the xattr name/value. Butxh_name_value_lenis 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.