UPSTREAM: 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 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>
(cherry picked from commit e2598077dc6a26c9644393e5c21f22a90dbdccdb)

Change-Id: I74cab93b5d5ce98e142c57790830804e9ce60d9c
Reviewed-on: https://chromium-review.googlesource.com/1279325
Commit-Ready: Aditya Kali <adityakali@google.com>
Tested-by: Aditya Kali <adityakali@google.com>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
Reviewed-by: Trevor Bourget <bourget@google.com>
(cherry picked from commit 8113d696b7926fc688666028a345e4aa02ef98e1)
Reviewed-on: https://chromium-review.googlesource.com/c/1297534
Tested-by: Robert Kolchmeyer <rkolchmeyer@google.com>
1 file changed