public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Sun Ke <sunke32@huawei.com>
To: Chao Yu <chao@kernel.org>, <fstests@vger.kernel.org>, <guan@eryu.me>
Subject: Re: [PATCH] common/attr: _acl_get_max echo 532 for f2fs
Date: Mon, 7 Feb 2022 11:07:49 +0800	[thread overview]
Message-ID: <99dd767d-eb52-44ff-ecaf-059cf3623c29@huawei.com> (raw)
In-Reply-To: <6dbebe97-b29d-ede4-79cf-4d66b2d44c01@kernel.org>



在 2022/1/30 23:07, Chao Yu 写道:
> On 2022/1/30 17:28, Sun Ke wrote:
>> Run generic/026 on f2fs, the diff:
>>
>>      -chacl: cannot set access acl on "largeaclfile": Argument list 
>> too long
>>      +Wrong ACL count - 532 != 531
>>
>> The ACL_MAX_ENTRIES depend on MAX_VALUE_LEN(inode), 
>> MAX_VALUE_LEN(inode) I got
>> by printk is 4244, so I think the ACL_MAX_ENTRIES should be
>> (4244 - 20) / 8 + 4 =532.
>>
>> Signed-off-by: Sun Ke <sunke32@huawei.com>
> 
> FYI:
> 
> https://patchwork.kernel.org/project/fstests/patch/20170428131307.3384-1-chao@kernel.org/ 
> 
> 
> I've update the patch based on Jaegeuk's comments, however, I forgot to 
> send it to
> mailing list, so could you please check revised one below?
> 
>  From 68965c837fd04795064b352589e3f7005e6d75f5 Mon Sep 17 00:00:00 2001
> From: Chao Yu <chao@kernel.org>
> Date: Fri, 28 Apr 2017 20:51:11 +0800
> Subject: [PATCH v2] 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 'inline_xattr' in fs option.
> 
> Additionally, f2fs has changed disk layout of xattr block a bit, so will
> contain one more entry in both inline and noinline xattr inode, this patch
> will modify the max acl number to adjust it.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> v2:
> - adjust the config for old kernel as well.
>   common/attr | 11 ++++++++---
>   1 file changed, 8 insertions(+), 3 deletions(-)
> 
> diff --git a/common/attr b/common/attr
> index 35682d7c..6377a936 100644
> --- a/common/attr
> +++ b/common/attr
> @@ -26,11 +26,16 @@ _acl_get_max()
>           echo 8191
>           ;;
>       f2fs)
> -        _fs_options $TEST_DEV | grep "inline_xattr" >/dev/null 2>&1
> +        _fs_options $TEST_DEV | grep "noinline_xattr" >/dev/null 2>&1
>           if [ $? -eq 0 ]; then
> -            echo 531
> +            echo 507
>           else
> -            echo 506
> +            _fs_options $TEST_DEV | grep "inline_xattr" >/dev/null 2>&1
> +            if [ $? -eq 0 ]; then
> +                echo 532
> +            else
> +                echo 507
> +            fi
>           fi
>           ;;
>       bcachefs)

Sorry for reply late.

I send a v2 patch base on your patch, right?

Thanks,
Sun Ke

  parent reply	other threads:[~2022-02-07  6:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30  9:28 [PATCH] common/attr: _acl_get_max echo 532 for f2fs Sun Ke
2022-01-30 15:07 ` Chao Yu
2022-02-01 17:53   ` Eric Biggers
2022-02-03 14:30     ` Chao Yu
2022-02-07  3:07   ` Sun Ke [this message]
2022-02-07 15:46     ` Chao Yu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99dd767d-eb52-44ff-ecaf-059cf3623c29@huawei.com \
    --to=sunke32@huawei.com \
    --cc=chao@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox