From: Eryu Guan <eguan@redhat.com>
To: Chao Yu <chao@kernel.org>
Cc: fstests@vger.kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH] attr: adbjust acl_max of f2fs
Date: Wed, 3 May 2017 15:29:43 +0800 [thread overview]
Message-ID: <20170503072943.GE7250@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170428131307.3384-1-chao@kernel.org>
On Fri, Apr 28, 2017 at 09:13:07PM +0800, Chao Yu wrote:
> From: Chao Yu <yuchao0@huawei.com>
>
> 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 'ininline_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 <yuchao0@huawei.com>
Thanks for the patch! It looks fine to me from fstests POV, but need
review from f2fs developers too.
Thanks,
Eryu
> ---
> common/attr | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/common/attr b/common/attr
> index ac139e61..6d4f68ed 100644
> --- a/common/attr
> +++ b/common/attr
> @@ -43,11 +43,11 @@ _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
> + echo 532
> fi
> ;;
> *)
> --
> 2.12.2.575.gb14f27f
>
next prev parent reply other threads:[~2017-05-03 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 13:13 [PATCH] attr: adbjust acl_max of f2fs Chao Yu
2017-05-03 7:29 ` Eryu Guan [this message]
2017-05-03 8:07 ` Chao Yu
2017-05-03 17:02 ` Jaegeuk Kim
2017-05-04 15:32 ` Chao Yu
2017-05-04 17:39 ` Jaegeuk Kim
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=20170503072943.GE7250@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).