summaryrefslogtreecommitdiff
path: root/security/integrity
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2017-07-06 17:54:21 +0300
committerMimi Zohar <zohar@linux.vnet.ibm.com>2017-12-18 17:43:49 +0300
commit02c324a55ed9ee4d790eaa9ac8e7cdecbe3e0a22 (patch)
treea42d691de5e9bb798b31887bdecbc81a6073654e /security/integrity
parent9c655be0644429b71396347887b43676ab4f6781 (diff)
downloadlinux-02c324a55ed9ee4d790eaa9ac8e7cdecbe3e0a22.tar.xz
integrity: remove unneeded initializations in integrity_iint_cache entries
The init_once routine memsets the whole object to 0, and then explicitly sets some of the fields to 0 again. Just remove the explicit initializations. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
Diffstat (limited to 'security/integrity')
-rw-r--r--security/integrity/iint.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/security/integrity/iint.c b/security/integrity/iint.c
index d726ba23a178..fc38ca08dbb5 100644
--- a/security/integrity/iint.c
+++ b/security/integrity/iint.c
@@ -153,15 +153,11 @@ static void init_once(void *foo)
struct integrity_iint_cache *iint = foo;
memset(iint, 0, sizeof(*iint));
- iint->version = 0;
- iint->flags = 0UL;
- iint->atomic_flags = 0;
iint->ima_file_status = INTEGRITY_UNKNOWN;
iint->ima_mmap_status = INTEGRITY_UNKNOWN;
iint->ima_bprm_status = INTEGRITY_UNKNOWN;
iint->ima_read_status = INTEGRITY_UNKNOWN;
iint->evm_status = INTEGRITY_UNKNOWN;
- iint->measured_pcrs = 0;
mutex_init(&iint->mutex);
}