Re: [PATCH v2 4/5] jfs: cache NULL when both default_acl and acl are NULL
cgxu519 <[email protected]> Wed, 5 Sep 2018 14:13:47 +0800
| Newsgroups | gmane.comp.file-systems.jfs.general |
|---|---|
| Message-ID | <c231d198-7a4e-63a0-0a7d-9211ab0abfe9__47757.3589691476$1536128016$gmane$org@gmx.com> |
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 <[email protected]> > Acked-by: Dave Kleikamp <[email protected]> > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot