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 0d73a55208
("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>
This commit is contained in:
parent
7825cd83fa
commit
e2598077dc
@ -74,6 +74,7 @@ static void iint_free(struct integrity_iint_cache *iint)
|
|||||||
iint->ima_hash = NULL;
|
iint->ima_hash = NULL;
|
||||||
iint->version = 0;
|
iint->version = 0;
|
||||||
iint->flags = 0UL;
|
iint->flags = 0UL;
|
||||||
|
iint->atomic_flags = 0UL;
|
||||||
iint->ima_file_status = INTEGRITY_UNKNOWN;
|
iint->ima_file_status = INTEGRITY_UNKNOWN;
|
||||||
iint->ima_mmap_status = INTEGRITY_UNKNOWN;
|
iint->ima_mmap_status = INTEGRITY_UNKNOWN;
|
||||||
iint->ima_bprm_status = INTEGRITY_UNKNOWN;
|
iint->ima_bprm_status = INTEGRITY_UNKNOWN;
|
||||||
|
Loading…
Reference in New Issue
Block a user