Re: [PATCH v2 4/5] jfs: cache NULL when both default_acl and acl are NULL
Dave Kleikamp <[email protected]> Wed, 5 Sep 2018 07:28:34 -0500
| Newsgroups | gmane.comp.file-systems.jfs.general |
|---|---|
| Message-ID | <582c17b3-5d52-24c0-8d95-af3d62071738__30233.1257182688$1536150409$gmane$org@oracle.com> |
On 9/5/18 1:13 AM, cgxu519 wrote: > > 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. I'll take care of this one. Thanks, Shaggy > > 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