ima: re-initialize iint->atomic_flags
authorMimi Zohar <zohar@linux.vnet.ibm.com>
Tue, 23 Jan 2018 15:00:41 +0000 (10:00 -0500)
committerJames Morris <jmorris@namei.org>
Fri, 2 Feb 2018 10:03:08 +0000 (21:03 +1100)
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

index fc38ca0..9700e96 100644 (file)
@@ -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;