ext4: cache NULL when both default_acl and acl are NULL
authorChengguang Xu <cgxu519@gmx.com>
Sun, 7 Oct 2018 02:40:34 +0000 (22:40 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 7 Oct 2018 02:40:34 +0000 (22:40 -0400)
commit6fd941784b8ac3e74313f7112f0586076dc36544
tree9868e0e24c6fc12c560ff33e993f2c11250c6abd
parent8a98ec7c7b3901330a036af0f62f523c31d763da
ext4: cache NULL when both default_acl and acl are NULL

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.  However,
when default_acl and acl are NULL then they keep the value of
ACL_NOT_CACHED.  This patch changes the code to cache NULL for acl /
default_acl in this case to save unnecessary ACL lookup attempt.

Signed-off-by: Chengguang Xu <cgxu519@gmx.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Jan Kara <jack@suse.cz>
fs/ext4/acl.c