Re: [PATCH] integrity: get rid of unneeded initializations in integrity_iint_cache entries

From: Serge E. Hallyn
Date: Thu Jul 06 2017 - 11:05:01 EST


Quoting Jeff Layton (jlayton@xxxxxxxxxx):
> From: Jeff Layton <jlayton@xxxxxxxxxx>
>
> 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@xxxxxxxxxx>

Reviewed-by: Serge Hallyn <serge@xxxxxxxxxx>

> ---
> security/integrity/iint.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/security/integrity/iint.c b/security/integrity/iint.c
> index 6fc888ca468e..187b7cb378be 100644
> --- a/security/integrity/iint.c
> +++ b/security/integrity/iint.c
> @@ -153,14 +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->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;
> }
>
> static int __init integrity_iintcache_init(void)
> --
> 2.13.0