From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-integrity@vger.kernel.org, James Morris <jmorris@namei.org>
Subject: Re: linux-next: Tree for Dec 14 (security/integrity/ima/)
Date: Fri, 14 Dec 2018 15:26:50 -0500 [thread overview]
Message-ID: <20181214202650.GO11670@windriver.com> (raw)
In-Reply-To: <1544815174.3681.16.camel@linux.ibm.com>
[Re: linux-next: Tree for Dec 14 (security/integrity/ima/)] On 14/12/2018 (Fri 14:19) Mimi Zohar wrote:
> [Cc'ing Paul Gortmaker]
>
> On Fri, 2018-12-14 at 08:25 -0800, Randy Dunlap wrote:
> > On 12/13/18 11:18 PM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20181213:
> > >
> >
> > on i386:
> >
> > CC security/integrity/ima/ima_main.o
> > ../security/integrity/ima/ima_main.c: In function 'ima_load_data':
> > ../security/integrity/ima/ima_main.c:535:3: error: implicit declaration of function 'is_module_sig_enforced' [-Werror=implicit-function-declaration]
> > sig_enforce = is_module_sig_enforced();
> > ^
> >
> >
> > Needs:
>
> Commit 4f83d5ea643a ("security: integrity: make ima_main explicitly
> non-modular") just removed module.h.
Yes, unfortunately the security directory has additional confusion
because there is name space overlap between "module" as used in Linux
Security Module, and "module" as in "insmod foo.ko". The ima_main
is not modular, but it does use modular infrastructure to load others.
Fortunately this was the final commit in the series, so it can be
removed or reverted as per maintainer's choice. In the meantime, I'll
look into why my "allyesconfig" build testing didn't pick up on this,
so I can close that testing gap.
Randy, if you were using one of your usual "randconfig" builds, maybe
you can mail me the .config out of band - no need spamming the lists.
Thanks, and sorry for the undetected fallout.
Paul.
--
>
> Mimi
>
>
> >
> > ---
> > security/integrity/ima/ima_main.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > --- linux-next-20181214.orig/security/integrity/ima/ima_main.c
> > +++ linux-next-20181214/security/integrity/ima/ima_main.c
> > @@ -24,6 +24,7 @@
> > #include <linux/init.h>
> > #include <linux/file.h>
> > #include <linux/binfmts.h>
> > +#include <linux/module.h>
> > #include <linux/mount.h>
> > #include <linux/mman.h>
> > #include <linux/slab.h>
> >
> >
> >
>
next prev parent reply other threads:[~2018-12-14 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 7:18 linux-next: Tree for Dec 14 Stephen Rothwell
2018-12-14 16:25 ` linux-next: Tree for Dec 14 (security/integrity/ima/) Randy Dunlap
2018-12-14 19:19 ` Mimi Zohar
2018-12-14 20:26 ` Paul Gortmaker [this message]
2018-12-14 22:28 ` Paul Gortmaker
2018-12-20 18:00 ` James Morris
2018-12-15 15:51 ` linux-next: Tree for Dec 14 Guenter Roeck
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=20181214202650.GO11670@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--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).