From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-integrity@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 14 (security/integrity/ima/)
Date: Fri, 14 Dec 2018 08:25:32 -0800 [thread overview]
Message-ID: <8205aafb-bbc1-2196-17d9-e70e9ac56c2e@infradead.org> (raw)
In-Reply-To: <20181214181826.5775b958@canb.auug.org.au>
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:
---
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>
--
~Randy
next parent reply other threads:[~2018-12-14 16:25 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 ` Randy Dunlap [this message]
2018-12-14 19:19 ` linux-next: Tree for Dec 14 (security/integrity/ima/) Mimi Zohar
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=8205aafb-bbc1-2196-17d9-e70e9ac56c2e@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).