From: Mimi Zohar <zohar@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: 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 14:19:34 -0500 [thread overview]
Message-ID: <1544815174.3681.16.camel@linux.ibm.com> (raw)
In-Reply-To: <8205aafb-bbc1-2196-17d9-e70e9ac56c2e@infradead.org>
[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.
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 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181214181826.5775b958@canb.auug.org.au>
2018-12-14 16:25 ` linux-next: Tree for Dec 14 (security/integrity/ima/) Randy Dunlap
2018-12-14 19:19 ` Mimi Zohar [this message]
2018-12-14 20:26 ` Paul Gortmaker
2018-12-14 22:28 ` Paul Gortmaker
2018-12-20 18:00 ` James Morris
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=1544815174.3681.16.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).