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>,
David Howells <dhowells@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-integrity@vger.kernel.org,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 26 (security/integrity/ima/)
Date: Thu, 27 Jun 2019 09:02:14 -0400 [thread overview]
Message-ID: <1561640534.4101.124.camel@linux.ibm.com> (raw)
In-Reply-To: <ee503bc1-a588-81f5-47e0-1762f590662f@infradead.org>
[Cc'ing David Howells]
On Wed, 2019-06-26 at 11:35 -0700, Randy Dunlap wrote:
> On 6/26/19 6:16 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > The sparc64 builds are broken in this tree, sorry.
> >
> > Changes since 20190625:
> >
>
> on x86_64:
>
> 11 warnings like this one (in a randconfig build):
>
> CC security/integrity/ima/ima_fs.o
> In file included from ../security/integrity/ima/ima.h:25:0,
> from ../security/integrity/ima/ima_fs.c:26:
> ../security/integrity/ima/../integrity.h:170:18: warning: ‘struct key_acl’ declared inside parameter list [enabled by default]
> struct key_acl *acl)
> ^
> ../security/integrity/ima/../integrity.h:170:18: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
David, CONFIG_INTEGRITY_SIGNATURE is dependent on KEYS being enabled,
but the stub functions are not. There's now a dependency on
key_acl().
Mimi
next prev parent reply other threads:[~2019-06-27 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:16 linux-next: Tree for Jun 26 Stephen Rothwell
2019-06-26 16:01 ` linux-next: Tree for Jun 26 (task_struct: cached_requested_key) Randy Dunlap
2019-06-26 18:35 ` linux-next: Tree for Jun 26 (security/integrity/ima/) Randy Dunlap
2019-06-27 13:02 ` Mimi Zohar [this message]
2019-06-27 13:29 ` David Howells
2019-06-27 15:08 ` Randy Dunlap
2019-06-26 19:59 ` linux-next: Tree for Jun 26 (task_struct: cached_requested_key) David Howells
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=1561640534.4101.124.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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).