From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: fstests@vger.kernel.org, eguan@redhat.com,
linux-f2fs-devel@lists.sourceforge.net,
Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH] attr: adbjust acl_max of f2fs
Date: Thu, 4 May 2017 10:39:19 -0700 [thread overview]
Message-ID: <20170504173919.GA7464@jaegeuk.local> (raw)
In-Reply-To: <3c80f5f0-f68e-a6f6-b355-fd5e0fcdbe76@kernel.org>
On 05/04, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 2017/5/4 1:02, Jaegeuk Kim wrote:
> > Hello,
> >
> > On 04/28, 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>
> >> ---
> >> 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
> >
> > This breaks old kernel support which has no "noinline_xattr". It'd be good to
> > check "inline_xattr" again after checking "noinline_xattr". And, in terms of
>
> Hmm, we have changed xattr layout a bit in new kernel, so even we have
> knew that user set inline_xattr mount option, still we don't know
> whether the last kernel was been used, so we can not decide to choose
> 532 or 531 as acl_max value. Maybe we need to check result of 'uname -r'
> either.
>
> > different number of entries, can we get the number from local.config by adding
> > an export symbol likewise FSTYP?
>
> You mean adding one more configuration parameter which can be defined by
> user, then _acl_get_max can return correct acl_max value depend on that
> parameter?
How about this?
if noinline_xattr exists
acl_max=506
else if inline_xattr exists
acl_max=531
else
/* for old kernel */
acl_max=506
fi
if $ACL_MAX_ADJ is defined; then
acl_max += $ACL_MAX_ADJ;
fi
Thanks,
>
> Thanks,
>
> >
> > Thanks,
> >
> >> if [ $? -eq 0 ]; then
> >> - echo 531
> >> + echo 507
> >> else
> >> - echo 506
> >> + echo 532
> >> fi
> >> ;;
> >> *)
> >> --
> >> 2.12.2.575.gb14f27f
prev parent reply other threads:[~2017-05-04 17:39 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
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 [this message]
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=20170504173919.GA7464@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=eguan@redhat.com \
--cc=fstests@vger.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).