[f2fs-dev] [PATCH v3] generic/066: attr1 is still there after log replay on f2fs

The test fail on f2fs: xattr names and values after second fsync log replay: # file: SCRATCH_MNT/foobar +user.attr1="val1" user.attr3="val3" attr1 is still there after log replay. f2fs doesn't support fs-op level transaction functionality. so it have no way to persist all metada

Re: [f2fs-dev] [PATCH v2] generic/066: attr1 is still there after log replay on f2fs

在 2022/3/15 12:01, Chao Yu 写道: On 2022/3/11 17:43, Sun Ke via Linux-f2fs-devel wrote: The test fail on f2fs:   xattr names and values after second fsync log replay:   # file: SCRATCH_MNT/foobar +user.attr1="val1"   user.attr3="val3" attr1 is still th

[f2fs-dev] [PATCH v2] generic/066: attr1 is still there after log replay on f2fs

The test fail on f2fs: xattr names and values after second fsync log replay: # file: SCRATCH_MNT/foobar +user.attr1="val1" user.attr3="val3" attr1 is still there after log replay. f2fs doesn't support fs-op level transaction functionality. so it have no way to persist all metada

Re: [f2fs-dev] [PATCH] generic/066: attr1 is still there after log replay on f2fs

在 2022/3/10 15:33, Chao Yu 写道: On 2022/3/10 9:41, Dave Chinner wrote: On Wed, Mar 09, 2022 at 03:34:27PM +0800, Chao Yu wrote: On 2022/3/9 14:22, Dave Chinner wrote: On Wed, Mar 09, 2022 at 12:31:17PM +0800, Chao Yu wrote: On 2022/2/28 11:57, Sun Ke via Linux-f2fs-devel wrote: The test

Re: [f2fs-dev] [PATCH] generic/066: attr1 is still there after log replay on f2fs

Friendly ping... 在 2022/2/28 11:57, Sun Ke 写道: The test fail on f2fs: xattr names and values after second fsync log replay: # file: SCRATCH_MNT/foobar +user.attr1="val1" user.attr3="val3" attr1 is still there after log replay. I guess it is f2fs's special feature to impro

[f2fs-dev] [PATCH] generic/066: attr1 is still there after log replay on f2fs

The test fail on f2fs: xattr names and values after second fsync log replay: # file: SCRATCH_MNT/foobar +user.attr1="val1" user.attr3="val3" attr1 is still there after log replay. I guess it is f2fs's special feature to improve the performance. Signed-off-by: Sun Ke --- Is it

Re: [f2fs-dev] [PATCH] common/attr: adbjust acl_max of f2fs

Friendly ping... 在 2022/2/8 15:16, Sun Ke 写道: f2fs has set inline_xattr as a default option, and introduced a new option named 'noinline_xattr' for disabling default inline_xattr option. So in _acl_get_max we need to check 'noinline_xattr' string in fs option, otherwise we may select the wrong m

[f2fs-dev] [PATCH] common/attr: adbjust acl_max of f2fs

f2fs has set inline_xattr as a default option, and introduced a new option named 'noinline_xattr' for disabling default inline_xattr option. So in _acl_get_max we need to check 'noinline_xattr' string in fs option, otherwise we may select the wrong max acl number since we always found the string 'i