[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <900e5d34-f95a-279d-2d1b-bd8333be7f55@kernel.org>
Date: Sun, 2 Sep 2018 15:55:52 +0800
From: Chao Yu <chao@...nel.org>
To: Chengguang Xu <cgxu519@....com>, jack@...e.com, tytso@....edu,
adilger.kernel@...ger.ca, jaegeuk@...nel.org, yuchao0@...wei.com,
shaggy@...nel.org, hubcap@...ibond.com, martin@...ibond.com
Cc: jfs-discussion@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, linux-ext4@...r.kernel.org,
devel@...ts.orangefs.org
Subject: Re: [f2fs-dev] [PATCH v2 3/5] f2fs: cache NULL when both default_acl
and acl are NULL
On 2018/8/31 22:33, Chengguang Xu wrote:
> default_acl and acl of newly created inode will be initiated
> as ACL_NOT_CACHED in vfs function inode_init_always() and later
> will be updated by calling xxx_init_acl() in specific filesystems.
> Howerver, when default_acl and acl are NULL then they keep the value
> of ACL_NOT_CACHED, this patch tries to cache NULL for acl/default_acl
> in this case.
>
> Signed-off-by: Chengguang Xu <cgxu519@....com>
Acked-by: Chao Yu <yuchao0@...wei.com>
Thanks,
Powered by blists - more mailing lists