summaryrefslogtreecommitdiffstats
path: root/security/integrity/iint.c
diff options
context:
space:
mode:
authorMimi Zohar <zohar@linux.vnet.ibm.com>2018-01-23 16:00:41 +0100
committerJames Morris <jmorris@namei.org>2018-02-02 11:03:08 +0100
commite2598077dc6a26c9644393e5c21f22a90dbdccdb (patch)
treee84d4c3eff64cff1b940bab29bd85f57467725d0 /security/integrity/iint.c
parentmaintainers: update trusted keys (diff)
downloadlinux-e2598077dc6a26c9644393e5c21f22a90dbdccdb.tar.xz
linux-e2598077dc6a26c9644393e5c21f22a90dbdccdb.zip
ima: re-initialize iint->atomic_flags
Intermittently security.ima is not being written for new files. This patch re-initializes the new slab iint->atomic_flags field before freeing it. Fixes: commit 0d73a55208e9 ("ima: re-introduce own integrity cache lock") Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com> Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'security/integrity/iint.c')
-rw-r--r--security/integrity/iint.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/security/integrity/iint.c b/security/integrity/iint.c
index fc38ca08dbb5..9700e96ab0f0 100644
--- a/security/integrity/iint.c
+++ b/security/integrity/iint.c
@@ -74,6 +74,7 @@ static void iint_free(struct integrity_iint_cache *iint)
iint->ima_hash = NULL;
iint->version = 0;
iint->flags = 0UL;
+ iint->atomic_flags = 0UL;
iint->ima_file_status = INTEGRITY_UNKNOWN;
iint->ima_mmap_status = INTEGRITY_UNKNOWN;
iint->ima_bprm_status = INTEGRITY_UNKNOWN;