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:43:00 +0000 (09:43 +0100)
commitd467320fdaf328fd6f98fc686b3a3fdd226dbaef
treea26c1d8845d6896045c48cd68ad5c2fa2ab4c5ca
parent281c07f30f71b4982cb535b633e5286bf0c7d056
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