[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c231d198-7a4e-63a0-0a7d-9211ab0abfe9@gmx.com>
Date: Wed, 5 Sep 2018 14:13:47 +0800
From: cgxu519 <cgxu519@....com>
To: Dave Kleikamp <dave.kleikamp@...cle.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: [Jfs-discussion] [PATCH v2 4/5] jfs: cache NULL when both
default_acl and acl are NULL
On 09/04/2018 04:34 AM, Dave Kleikamp wrote:
> Are you pushing these as a series, or would you like this patch pushed
> through the jfs tree?
I'd hope maintainers pick individual patch to their tree.
Thanks,
Chengguang
>
> On 8/31/18 9:33 AM, 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: Dave Kleikamp <dave.kleikamp@...cle.com>
>
Powered by blists - more mailing lists