ima: re-initialize iint->atomic_flags
authorMimi Zohar <zohar@linux.vnet.ibm.com>
Tue, 23 Jan 2018 15:00:41 +0000 (10:00 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 1 Dec 2018 08:44:26 +0000 (09:44 +0100)
commit1f89834896bb627dd54931519e148ea74ef53d05
tree606d6f14c5f41a6a394edc3b554e54a8097cea1d
parent166f4542ec59d1856a558f3b1ec482730c2a9b7f
ima: re-initialize iint->atomic_flags

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 <zohar@linux.vnet.ibm.com>
Signed-off-by: James Morris <jmorris@namei.org>
Cc: Aditya Kali <adityakali@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
security/integrity/iint.c