From: Austin Kim <austindh.kim@gmail.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: dmitry.kasatkin@gmail.com, "James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-integrity@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
김동현 <austin.kim@lge.com>, "Petko Manolov" <petkan@mip-labs.com>
Subject: Re: [PATCH] IMA: remove -Wmissing-prototypes warning
Date: Wed, 30 Jun 2021 07:40:50 +0900 [thread overview]
Message-ID: <CADLLry5D9T_icTSGOggb=3vJqYq9Qvq-WEhmfgJMCSGuPV0AAg@mail.gmail.com> (raw)
In-Reply-To: <fe6c853842425e675024731525e0f244da368e8e.camel@linux.ibm.com>
2021년 6월 29일 (화) 오후 11:30, Mimi Zohar <zohar@linux.ibm.com>님이 작성:
>
> [Cc: Petko Manolov <petkan@mip-labs.com>]
>
> Hi Austin,
>
> On Tue, 2021-06-29 at 14:50 +0100, Austin Kim wrote:
> > From: Austin Kim <austin.kim@lge.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@lge.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.
Oh! Thanks for information.
>
> thanks,
>
> Mimi
>
prev parent reply other threads:[~2021-06-29 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 13:50 [PATCH] IMA: remove -Wmissing-prototypes warning Austin Kim
2021-06-29 14:30 ` Mimi Zohar
2021-06-29 22:40 ` Austin Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADLLry5D9T_icTSGOggb=3vJqYq9Qvq-WEhmfgJMCSGuPV0AAg@mail.gmail.com' \
--to=austindh.kim@gmail.com \
--cc=austin.kim@lge.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=petkan@mip-labs.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).