commit e2598077dc6a26c9644393e5c21f22a90dbdccdb
author Mimi Zohar <zohar@linux.vnet.ibm.com> Tue Jan 23 10:00:41 2018 -0500
committer James Morris <jmorris@namei.org> Fri Feb 02 21:03:08 2018 +1100
tree e84d4c3eff64cff1b940bab29bd85f57467725d0
parent 7825cd83fad7a30328bc874062eb19bdb2fbb38b

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>

security/integrity/iint.c

diff --git a/security/integrity/iint.c b/security/integrity/iint.c
index fc38ca0..9700e96 100644
--- a/security/integrity/iint.c
+++ b/security/integrity/iint.c
@@ -74,6 +74,7 @@
 	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;