lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe6c853842425e675024731525e0f244da368e8e.camel@linux.ibm.com>
Date:   Tue, 29 Jun 2021 10:30:20 -0400
From:   Mimi Zohar <zohar@...ux.ibm.com>
To:     Austin Kim <austindh.kim@...il.com>, dmitry.kasatkin@...il.com,
        jmorris@...ei.org, serge@...lyn.com
Cc:     linux-integrity@...r.kernel.org,
        linux-security-module@...r.kernel.org,
        linux-kernel@...r.kernel.org, austin.kim@....com,
        Petko Manolov <petkan@...-labs.com>
Subject: Re: [PATCH] IMA: remove -Wmissing-prototypes warning

[Cc: Petko Manolov <petkan@...-labs.com>]

Hi Austin,

On Tue, 2021-06-29 at 14:50 +0100, Austin Kim wrote:
> From: Austin Kim <austin.kim@....com>
> 
> With W=1 build, the compiler throws warning message as below:
> 
>    security/integrity/ima/ima_mok.c:24:12: warning:
>    no previous prototype for ‘ima_mok_init’ [-Wmissing-prototypes]
>        __init int ima_mok_init(void)
> 
> Silence the warning by adding static keyword to ima_mok_init().
> 
> Signed-off-by: Austin Kim <austin.kim@....com>
> ---
>  security/integrity/ima/ima_mok.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/security/integrity/ima/ima_mok.c b/security/integrity/ima/ima_mok.c
> index 1e5c01916173..95cc31525c57 100644
> --- a/security/integrity/ima/ima_mok.c
> +++ b/security/integrity/ima/ima_mok.c
> @@ -21,7 +21,7 @@ struct key *ima_blacklist_keyring;
>  /*
>   * Allocate the IMA blacklist keyring
>   */
> -__init int ima_mok_init(void)
> +static __init int ima_mok_init(void)
>  {
>  	struct key_restriction *restriction;
>  

Thank you for the patch, which does fix the warning.   The .ima_mok
keyring was removed a while ago.  With all the recent work on the
system blacklist, I'm wondering if anyone is still using the IMA
blacklist keyring or whether it should be removed as well.

thanks,

Mimi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ