All of lore.kernel.org
 help / color / mirror / Atom feed
* [Ocfs2-devel] [PATCH 0/2] ocfs2: two fixes for xattr
@ 2009-02-11  2:33 Tiger Yang
  2009-02-11  2:38 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: set xh_free_start when xattr header in inode/block Tiger Yang
  2009-02-11  2:38 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: set gap to seperate entry and value when xattr in bucket Tiger Yang
  0 siblings, 2 replies; 9+ messages in thread
From: Tiger Yang @ 2009-02-11  2:33 UTC (permalink / raw)
  To: ocfs2-devel

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

^ permalink raw reply	[flat|nested] 9+ messages in thread
* [Ocfs2-devel] [PATCH 0/2] ocfs2: two fixes for xattr  -v2
@ 2009-02-16  7:38 Tiger Yang
  2009-02-16  7:43 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: set xh_free_start when xattr header in inode/block Tiger Yang
  0 siblings, 1 reply; 9+ messages in thread
From: Tiger Yang @ 2009-02-16  7:38 UTC (permalink / raw)
  To: ocfs2-devel

Hi,

I have fixed the problems in version 1 patches. These two patches based 
on the latest main line kernel.

Thanks,
tiger

> 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.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2009-02-19 17:38 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-11  2:33 [Ocfs2-devel] [PATCH 0/2] ocfs2: two fixes for xattr Tiger Yang
2009-02-11  2:38 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: set xh_free_start when xattr header in inode/block Tiger Yang
2009-02-11 18:50   ` Joel Becker
2009-02-12  3:02     ` Tiger Yang
2009-02-13 23:03       ` Joel Becker
2009-02-11  2:38 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: set gap to seperate entry and value when xattr in bucket Tiger Yang
  -- strict thread matches above, loose matches on Subject: below --
2009-02-16  7:38 [Ocfs2-devel] [PATCH 0/2] ocfs2: two fixes for xattr -v2 Tiger Yang
2009-02-16  7:43 ` [Ocfs2-devel] [PATCH 1/2] ocfs2: set xh_free_start when xattr header in inode/block Tiger Yang
2009-02-18  7:13   ` Tiger Yang
2009-02-19 17:38     ` Joel Becker

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.