4.9-stable review patch. If anyone has any objections, please let me know.
------------------ From: Mimi Zohar <[email protected]> commit e2598077dc6a26c9644393e5c21f22a90dbdccdb upstream. 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 <[email protected]> Signed-off-by: James Morris <[email protected]> Cc: Aditya Kali <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> --- security/integrity/iint.c | 1 + 1 file changed, 1 insertion(+) --- a/security/integrity/iint.c +++ b/security/integrity/iint.c @@ -74,6 +74,7 @@ static void iint_free(struct integrity_i 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;
