[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181007033645.GA12046@thunk.org>
Date: Sat, 6 Oct 2018 23:36:45 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: cgxu519 <cgxu519@....com>
Cc: adilger.kernel@...ger.ca, jack@...e.com, jaegeuk@...nel.org,
yuchao0@...wei.com, shaggy@...nel.org, hubcap@...ibond.com,
martin@...ibond.com, devel@...ts.orangefs.org,
linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
jfs-discussion@...ts.sourceforge.net
Subject: Re: [PATCH v2 2/5] ext4: cache NULL when both default_acl and acl
are NULL
On Wed, Sep 12, 2018 at 11:04:35PM +0800, cgxu519 wrote:
> On 08/31/2018 10:33 PM, 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>
Applied, thanks.
- Ted
Powered by blists - more mailing lists